In this onboarding tutorial, we'll go over how to configure and automate your incident response process with FireHydrant's Runbooks.

There are three main types of Runbooks you can configure in FireHydrant:

  • Incidents
  • Infrastructure (Functionality, Service, or Environment)
  • Incident Roles

For this article, we'll solely be covering Infrastructure Runbooks.

Infrastructure Runbooks

Infrastructure Runbooks are used to define steps that should be taken when responding to an incident when a given functionality, service, or environment is impacted. These steps can be either executed automatically or manually.

You can include links to relevant graphs, GitHub commits, external guides, and really anything that would be helpful to restore your infrastructure. For example, If you have a third-party application with a severe memory leak, but it's not safe to restart without following a specific shutdown process, that's a great candidate for becoming an Infrastructure Runbook.


Using Infrastructure Runbooks, you can now configure which steps you'd like to take during an incident when a specific infrastructure is impacted, whether that's adding an SME to the case, giving instructions, and more!

We'll now finish off our onboarding series by going over how to gain insights from our incidents in order to build for the future.

Did this answer your question?