Welcome to FireHydrant! We’re really happy to be a part of your team for fighting fires. We’re an incident response tool, but we also try to offer so many more tools for you as an operator of software. This document is to help get an understanding of FireHydrant and how to best utilize our Slack integration.
At its core, the FireHydrant Slack integration is designed to be a low-friction way of opening an incident, compiling notes and messages automatically, and assembling the right people fast. This guide should help get started with that.
Starting an incident with Slack
When you need to open an incident, you can type into Slack:
/firehydrant new Incident Name
Anything after the word “new” will be set as the incident’s name. FireHydrant will then open a new channel on your behalf once you select an environment or severity. Keep in mind these are optional, you can click “Open Incident” without selecting either and we’ll create the incident channel still.
The FireHydrant Slack integration will record all of the chatter and attachments pasted into the channel. (Ie: if you paste an image of a graph we’ll collect that image and store it in your timeline automatically).
A nice way you can inform other channels of the incident you’ve opened is by running:
/firehydrant notify #general
FireHydrant will post a message into the general chatroom about the incident once you run this.
Automatic Channel Notifications
Alternatively to notifying manually, FireHydrant allows you to configure channels that will always receive notifications about an incident. This is available by going to the Organization → Integrations → Configure Slack.
On this page, you’ll see a button to add a new automatic channel notification that will receive notifications automatically when a incident is opened via Slack.
Adding Services / Environments from Slack
Once you’re in the Slack channel for the incident (ie: #incident-343), you have the option to add services / environments to the incident as well. For example, if you want to add a service named “guilty-spark”, you can type in:
/firehydrant add service guilty-spark
If you can’t remember the exact name of a service you can also type in:
/firehydrant add service
Notice how we’re omitting the service key in this example, FireHydrant will send a dropdown back to Slack that will allow you to search for the service you’d like to add.
All of these commands also work for environments as well, you can run /firehydrant add environment the same way.
Notes and Status Updates
FireHydrant will collect all chat messages from a Slack room into your incident timeline automatically. If you’d like to post a more structured note about the incident, you can add a note from a Slack room by running:
/firehydrant add note We've identified the root cause of our outage and will be clogging the source of the flood in the next 30 minutes.
This adds a note to your incident as a separate type from a Slack message. This is valuable if you’d like to only add notes to your post mortem timeline in the future.
FireHydrant also comes with a private status page that you can send to other stakeholders in the organization (customer success, sales, etc). This page has a separate visibility for notes. To post to this page, you can run:
/firehydrant add status Currently experiencing a flood problem
Once a status is posted, it will look like this on the private status page.
Private status pages will stick around for 2 days after an incident and then will return a page not found after then.
FireHydrant allows you to configure as many incident roles as you like and assign default tasks to them (Order pizza, email the CEO, etc). These are valuable to quickly delegate responsibilities to responders on the incident.
To add assign a user to an incident, you can use their email to a role by typing:
/firehydrant assign role [email protected] commander
All of the roles you create in FireHydrant for your organization are available for assignment via this command.
When users are assigned roles, they’ll receive a direct message in Slack if they’ve linked their account saying they’ve been assigned the role. They’ll also receive tasks that are available via the Overview page in the Incident UI.
Resolving an Incident
Once you’ve fixed that pesky incident, you can mark it as resolved in the incident channel by typing:
This marks it as resolved for you.
We hope this guide is helpful! If you have any questions or suggestions, please email [email protected] and we’ll happily get back to you.