Running incidents and executing Runbooks can be done directly in Slack where your team is already accustomed to working. This article includes a list of FireHydrant's Slack commands.
There are a number of aliases that can be used to execute slack bot commands. The different aliases are as follows:
For the purpose of this article, we will utilize /firehydrant.
Provides help text and a list of available commands.
/firehydrant new incident [incident name]
Opens a dialog box asking for additional information to kick off a new incident. Here you can select the impacted environments and severity if known. Clicking Open from this dialog box creates a new Slack channel where all of your messaging is captured and sent to FireHydrant.
Allows you to see who's on-call for a particular service. This will only work if the was linked and/or imported from PagerDuty or Opsgenie.
Sends a prompt for you to link your Slack account with your FireHydrant account.
Allows you to edit the details of the incident. These details include the name, customer impact, description, infrastructure impacted, severity, and more.
Allows you to change the incident milestone and component status. From this section, you can also include a comment about why you are changing the status. If you have active status pages, you can post your update to the status pages as well.
/firehydrant add note [note text]
Adds a note (update) to the incident.
One way to think of notes are as pieces of information that are more important than normal chat messages. You can search a FireHydrant incident timeline and filter specifically by the content in a note (or notes) as opposed to typical chat messages.
/firehydrant add impact
This opens a text box where you can specify the available services, environments, and functionalities that are affected by a specific incident.
If you have teams associated with the service that you just added, FireHydrant will suggest adding those teams to the incident.
Add Action Item
/firehydrant add action-item
Allows you to Adds an action-item to the incident. Note that if you are utilizing our Jira or Clubhouse integrations, a subsequent ticket on the respective platform will also be created and linked to the original incident ticket created.
List Action Items
Lists out all the action items of the incident.
/firehydrant add runbook
Allows you to add a Runbook to the incident. Note that if a Runbook has already been added that it will not show up within the search bar.
Lists out all the Runbooks that are currently attached to the incident. This will also allow you to open a Runbook and execute steps right from Slack.
Page a Team
/firehydrant page team [team]
Pages a team in FireHydrant. Note that this will page a team based on the services a team is associated with in FireHydrant. These services must also be either linked with or imported from either PagerDuty or Opsgenie.
Page a Service
/firehydrant page service [service]
Pages a service from PagerDuty or Opsgenie. Note that these services must also be either linked with or imported from either PagerDuty or Opsgenie.
/firehydrant assign role
Assigning a role to someone with a linked Slack account sends that a direct message to that user, via Slack, informing them that they have been assigned a role to an active incident.
Assign a Team
/firehydrant assign team
Assigning a team brings sends a direct message each member on the team via Slack and also adds them into the channel. Note that each team member's Slack account will need to be linked to their FireHydrant account.
Incident Status Report
Displays a summary of the incident.
Allows you to update, add, or remove tags from an incident.
Resolve an Incident
This closes an incident and sets its status to resolved. A resolved incident continues to collect chat messages even after resolution, however, no commands pertaining to the incident can be executed. For re-opening incidents, you will need to do so within the command center.