Lifecycle of a runbook

Runbooks start as documented procedures on a piece of paper that can become fully automated procedures. Find out how can you move your documented procedures to fully automated runbooks.

Moving from manual to fully automated runbooks
Figure 1. Moving from manual to fully automated runbooks
The following steps outline the process of moving from documented procedures to fully automated runbooks:
  1. Transfer your documented procedures into a runbook.

    For more information, see Create a runbook.

  2. Assess the runbook and gather feedback. You can get information about the quality and the performance of the runbook by analyzing available metrics. For example, ratings, comments, success rate, and more.
    Draft comment: DEIRDRELAWTON
    Removed URL - TCT reported as broken link in NOI KC
  3. Create improved versions based on the feedback. With each new version, improve the success rate.

    For more information, see Runbook versions.

  4. Investigate which runbooks are suitable for automations. What steps can be put into an automated procedure? Not every runbook moves from a manual to a fully automated runbook. Carefully consider which steps you want to automate, depending on the comments received, the effort it takes to automate, the frequency the runbook is used, and the potential impact automated steps could have.

    For more information, see Creating an automation.

  5. Provide a new version with automated steps and see how it runs.

    For more information, see Managing automations.

  6. Continue to provide more automations until all steps are automated. Run runbooks that are started by a trigger.

    For more information, see Create a trigger.