Skip to main content

Execute Runbooks

Runbooks are predefined response procedures that guide you through incident remediation.

They can include automated actions (restart a service, scale infrastructure, query logs) and manual steps (verify with a customer, check a dashboard).

Executing runbooks during an incident ensures you follow standardized procedures rather than working from memory under pressure.

View Attached Runbooks​

Some runbooks are automatically attached to an incident based on the incident type and trigger conditions configured by your administrator.

  1. Open the Incident Details page.
  2. Click the Runbooks tab.
  3. Review any runbooks that are already attached.

Execute a Runbook​

  1. On the Runbooks tab, click Execute on an attached runbook — or click Execute Additional Runbook to add and run a different one.
  2. If adding a new runbook, search for or browse available runbooks, select the appropriate one, and confirm.
  3. Work through the steps in order:
    • Automated steps run on their own and report results (success, failure, output). Review the results before proceeding.
    • Manual steps provide instructions for you to follow. Mark each step complete as you go.
  4. Execution progress is logged in the incident timeline, giving full visibility to other responders and stakeholders.
  5. Click Close when execution is completed.

Choose the Right Runbook​

If you're unsure which runbook to use:

  • Check the incident type — Your administrator has likely associated recommended runbooks with each type. Auto-attached runbooks are the first place to look.
  • Browse the runbook library — Navigate to Runbooks in the left panel to see all available runbooks, their descriptions, and which incident types they're designed for.
  • Ask your team — If multiple runbooks seem applicable, check with teammates in the incident channel.

Best Practices​

  • Start with auto-attached runbooks — They're pre-selected for the incident type and are usually the most relevant first response.
  • Review automated step results before moving on — An automated step might fail or return unexpected output. Verify before proceeding to the next step.
  • Don't skip manual steps — Even if you think you know the procedure, follow the runbook. It exists to prevent steps from being missed during high-pressure situations.
  • Note deviations — If you need to deviate from the runbook (a step doesn't apply, you take a different action), document what you did in the incident timeline so it's captured for post-incident review.