Runbook Testing

Every Runbook in FireHydrant can be tested independently without going through the pain of declaring an incident. More specifically, when you execute a Runbook test, FireHydrant creates an incident with a GAMEDAY severity (therefore excluding it from metrics and analytics) and can isolate the Runbook so no other Runbooks execute.

Executing the Test

In this example, we have a simple Runbook containing an Asana step. Each time this Runbook executes, an incident task will be created in Asana in the project we've configured and selected.

1. To test any Runbook, click the "Test" button on the Runbook page. This will open a modal where you can confirm testing method.
   1. Testing Runbooks in isolation can be useful if you're trying to debug very specific things.
   2. On the other hand, it can be useful to uncheck this setting if you need to test a Runbook in conjunction with other Runbooks to see how your overall automation is configured.
2. Once you click "Confirm," you'll then be redirected to a test incident with only the selected Runbook attached (or others, depending on what you selected in the last step).
3. And voilà! In this example, you can see an Asana ticket has been created for this incident.

And we can see the ticket in Asana as well.

Troubleshooting Runbooks

In The Command Center, there is a dedicated tab for Runbooks and execution. On top of listing the Runbooks and all of the steps, you will also see the execution status of all steps.

Clicking on a dropdown will also show additional details like conditions and/or error messages if a step fails to execute. Use this to understand the state of your workflows and automation at any given time.

Step execution status can also be browsed from Slack within the incident channel with /fh runbooks.

Next Steps

• Read more about Runbook Best Practices
• Browse the available Runbook steps FireHydrant offers