Slack
Slack Integration allows you to:
- Create and track an incident right from Slack.
- Add incident events right from Slack.
- Add teams, services, functionalities impacted right from Slack.
- Assign users to roles to handle the incident efficiently right from Slack.
- Get related playbooks right into Slack to troubleshoot the incident efficiently.
- Get notified from all incident activities in a master channel eg. #incidents
- Page Opsgenie or Pagerduty teams right from Slack. ( If integrated )
You can set up this integration as a logged-in admin user on the integrations page found when you hover over your name:
Once inside of Integrations click Setup. From there Rootly will request permission to your Slack workspace. Click the green Allow button.
However, if you don't see Allow but instead see Request to install that means your Slack workspace needs to approve every app prior. In this case, provide a quick message (e.g. Using Rootly to improve our incident management) and click Submit.
Our Rootly Slack app will ask you the folllowing permissions in order to work correctly:
app_mentions:read: View messages that directly mention @rootly in conversations that the app is in.
commands: Add /rootly and /incident Slack shortcuts.
channels:manage: So we can create a public dedicated Slack channel.
channels:read: View basic information about public channels in a workspace.
groups:read: View basic information about private channels that Rootly has been added to.
groups:write: So we can create a private Slack channel for sensitive data ( eg: security ).
chat:write + chat:write.public: So we can write a beautiful welcome message in your dedicated incident Slack channel and respond to different actions.
files:read: So when you pin or react to a message in Slack, we can also save the file assocciated in Rootly timeline.
files:write: So our genius workflows can upload some files (console output) directly in Slack. We will never delete files in your Slack workspace.
pins:read: So we can add Slack message to your incident timeline through pinning.
reactions:read: So we can add Slack message to your incident timeline through a reaction of your choice.
reactions:write: So we can react to your message when we successfully added it to your incident timeline.
users.profile:read: So we can turn your Slack internal username to something more human (Firstname + Lastname)
usergroups:read: View user groups in a workspace (Aliases so you can invite @security people directly for example).
users:read + users:read.email: View email addresses of people in a workspace so you can invite them with one click. We will never invite them in your behalf.
Supported commands that can be used anywhere in Slack:
- /rootly create | new <title> - This will create a new incident with a dedicated channel.
- /rootly list - This will display a list of active incidents (10 max.)
- /rootly help - Shows available commands for interacting with the Rootly Slack bot
Supported commands that can only be used from an incident's Slack channel:
- /rootly add event <note> - This will create a new event and add it to the timeline event.
- /rootly add action item - This will create a new action item and add it to your incident.
- /rootly add task - This will create a new task and add it to your incident.
- /rootly add team - This will attach a team to an incident.
- /rootly add service - This will attach a service to an incident.
- /rootly add functionality - This will attach a functionality to an incident.
- /rootly escalate - This will escalate the incident to Pagerduty / Opsgenie / VictorOps.
- /rootly mitigate - This will mark an incident as mitigated.
- /rootly resolve - This will mark an incident as resolved.
- /rootly publish - This will publish an incident and make it visible to your public status pages.
Some settings are available as configuring Slack incident channel prefix and master incident channels to make sure your team is notified.
If you need help or more information about this integration, please contact support@rootly.io or use the lower right chat widget to get connected with an engineer.
You can uninstall this integration in the integrations panel by clicking Configure > Delete