Using Slack commands with FireHydrant

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:

  • /firehydrant
  • /fh
  • /incident

For the purpose of this article, we will utilize /firehydrant.

Help

/firehydrant help

Provides help text and a list of available commands.

New Incident

/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.

openanincident.png
 

On-call

/firehydrant on-call

Allows you to see who's on-call for a particular service.

Note: This will only work if the service was linked and/or imported from PagerDuty or Opsgenie.

/firehydrant link

Sends a prompt for you to link your Slack account with your FireHydrant account.

 

Edit Incident

/firehydrant edit

Allows you to edit the details of the incident. These details include the name, customer impact, description, infrastructure impacted, severity, and more.

 

Update Incident

/firehydrant update

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.

updateimpact.png

 

Add Note

/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.

 

Add Impact

/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.

add_impact.png
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: If you are using our Jira or Clubhouse integrations, a subsequent ticket on the respective service will also be created and linked to the original incident ticket.

 

List Action Items

/firehydrant action-items

Lists out all the action items of the incident.

 

Add Runbook

/firehydrant add runbook

Allows you to add a Runbook to the incident.

Note: If a Runbook has already been added, it will not appear in the search bar.

 

Runbooks

/firehydrant runbooks

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. This command pages a team based on the services the team is associated with in FireHydrant. These services must also be linked with (or imported from) either PagerDuty or Opsgenie.

Note: This will send a page to all services associated with this team.

 

Page a Service

/firehydrant page service [service]

Pages a service from PagerDuty or Opsgenie. These services must also be either linked with or imported from either PagerDuty or Opsgenie.

 

Assign Role

/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.

newroleassigned.png
 

Assign a Team

/firehydrant assign team

Assigning a team sends a direct message to each team member via Slack and adds them into the channel. Each team member's Slack account must be linked to their FireHydrant account.

 

Incident Status Report

/firehydrant status

Displays a summary of the incident.

 

Incident Tags

/firehydrant tags

Allows you to update, add, or remove tags from an incident.

 

Resolve an Incident

/firehydrant resolve

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. To re-open an incident, you must go to the command center.

Was this article helpful?
1 out of 1 found this helpful
Register your product
You can get support that’s tailored to you, owner exclusives and more
Our helpline hours:
8:00am - 8:00pm CST Monday to Friday; 9:00am - 6:00pm CST Saturday
Follow us on Twitter
Get the latest news and updates first