Runbooks Pages

The various Runbooks page are for working with the different runbook types in your configuration:

• Incident Runbooks — Automated investigations that execute in response to triggers.

• Lifecycle Runbooks — Runbooks that track the status of ongoing incidents and execute actions when the incident status changes.

• On-Demand Runbooks — Investigations that you execute manually rather than automatically.

• Subflows — Sequences of runbook nodes that execute discrete actions and that are saved as independent reusable components for inclusion in other runbooks.

Access these pages at any time by clicking the corresponding item in the Navigation pane at the left of the Riverbed IQ window.

Each Runbook page lists all the runbooks (or subflows) of that type that exist in your configuration (built-in and custom), enabling you to edit existing ones, create new ones, import and export them via JSON file, and delete any that you no longer need.

Filtering the List of Runbooks

You can control which runbooks are listed by choosing a filter; each filter shows how many runbooks it comprises:

• All Runbooks — Show all existing runbooks. This is the default.

• Automation Allowed — Show only those runbooks that have been enabled to be mapped to trigger types.

• Created By Me — Show only those runbooks created and saved using the current user account.

• In Error — Show only those runbooks marked with an error state. These runbooks cannot be be set to Active, and cannot be executed until all errors are corrected.

• Built-In — Show only those runbooks provided by Riverbed IQ application.

Working On an Existing Runbook

For any runbook, click on its row or click the > at its left to show its definition as a sequence of nodes. Doing this also makes several controls available:

• Edit — Open the runbook in the Runbook editor to change it.

• Export — Write the runbook definition to JSON file.

• Duplicate — Make a copy of the runbook.

• Delete — Use with caution. This will prompt you for confirmation, then will permanently remove the runbook from the system. There is no undo, once the runbook is deleted.

Creating a New Runbook

Two controls reside at the top of the page:

• New — Open the Runbook Editor to create a new runbook.

• Import — – Create a new runbook by importing a JSON file of a previously exported runbook definition.

Runbook List Columns

These fields are shown for each runbook on the Runbooks page. For each column, you can sort by it, and you can click on the Funnel icon to search or filter by a value.

• Runbook — The runbook's name. This may be user-defined, or auto-generated if no user has renamed it.

• Description — A brief, user-defined explanation of what the runbook is used for.

• Trigger — The type of trigger that launches the runbook.

• Entity Type — For on-demand runbooks only, the type of network object for which the runbook will execute.

• Built-In — A checkmark is shown if the runbook is provided by Riverbed IQ.

• Last Updated — The timestamp from when the runbook was most recently saved.

• Last Updated By — The username of the account that saved the most recent change to the runbook.

• Allow Automation — For all trigger types mapped to the runbook, toggle the runbook On to enable it or toggle it Off to disable it. This control is inaccessible if the runbook has any errors.
  A runbook must be On to be mappable to a trigger type in the Automation page; if it is Off, it will not be listed in the Edit Mapping dialog as available to be mapped. If a runbook is Off, it will not execute when a mapped trigger fires, but an incident still will be created; this can be useful if you want to modify the runbook and don't want it to execute in an experimental or unvalidated state. Custom runbooks are Off by default.

• Run button — For on-demand runbooks only, execute the runbook now. The runbook's output will be listed on the Runbook Analyses page.

• ... pop-up menu — Additional controls for managing runbooks. Most are also available from other places when working with runbooks.

  • Export — – Output the runbook definition to a JSON file that can be imported subsequently to create a new runbook.

  • Edit — Open the runbook in the Runbook Editor to change it.

  • Duplicate — Copy the runbook.

  • Delete — Use with caution. This will prompt you for confirmation, then will permanently remove the runbook from the system. There is no undo, once the runbook is deleted.

  • Test Run — Execute the runbook's logic immediately, without having to wait for a corresponding trigger.

  • Preview Output — Show what data the runbook will generate after it executes in response to a trigger.