In this onboarding tutorial, we'll go over how to configure and automate your incident response process with FireHydrant's Runbooks. This is a great way to equip your team with the proper gear to douse fires as they come in.
There are three main types of Runbooks you can configure in FireHydrant:
- Infrastructure (Functionality, Service, or Environment)
- Incident Roles
In this article, we'll focus solely on Incident Runbooks.
You can think of Incident Runbooks as your personal incident response playbook that will either manually or automatically execute given the severity of an incident that is initially declared on FireHydrant.
If you were to have a SEV1, SEV2, and SEV3 defined in FireHydrant, for instance, you would be able to create three separate Runbooks assigned to each respective severity. You'd also be able to have a single Runbook assigned to multiple severities (in this case all three).
Creating an Incident Runbook
To create a new Incident Runbook, you'll want to navigate over to the Runbooks page. From here, click on the "New" button to create a new Runbook.
On the following page, you'll need to type in a name for your Runbook. For the runbook type, make sure to select "Incident" (this should be set by default). Once confirmed, you can click on "Continue to configuration".
An example can be found below when creating a SEV3 Incident Runbook:
We'd recommend adding a short summary on what the Runbook is used for as well as assigning it to a severity.
Using the same example for our SEV3 Incident Runbook, we can see that we've added a summary of "Used for all SEV3 incidents", as well as attached the Runbook to a SEV3. This would mean that for every SEV3 incident declared on FireHydrant, this Runbook would automatically be attached.
Note: You'll have a dropdown menu under "Assign items related to this runbook" that will allow you to select which severity(s) you'd like to assign to the runbook as shown below.
Using Incident Runbooks, you can now configure which steps you'd like to take during an incident, whether that's notifying team members, creating tickets on JIRA, or updating a status page!
From here, we'll now wrap up our onboarding series by ensuring an easy way to keep tabs of our digital properties whenever there's a fire.