Automation Management Page

Click Automation > Automation Management in the Navigation pane to display the Automation Management page. The Automation Management page collects and shows the set of automations that are configured for your Riverbed IQ installation, organized by trigger category and type.

The Automation Management page shows trigger categories and types as a set of cards, one card for each trigger type:

• New Incident Triggers — The set of automated triggers configured for network phenomena comprising outages, congestion, anomalies, etc.

• Incident Lifecycle Triggers — The set of automated triggers configured for tracking changes to the incidents themselves, comprising status changes, priority changes, annotations, etc.

• External Triggers — The set of automated triggers configured for external API activity.

For each category, click the + to add an automated trigger for that category. This launches the Add an Automation wizard.

Each card shows the number of automations for that trigger type. Click the card to open a list of the corresponding automations; the automations are shown in the user-defined order in which they are executed according to their conditions being matched. The list shows these fields for each automation:

• Trigger — This is one of the built-in triggering entities, as listed in the Runbook Editor: Application Location Performance Issue, Device Down Issue, Interface Performance Issue, Multi-Device Down Issue, or Webhook.

• Execute On Trigger — This shows the name of the runbook that is associated with the trigger type. Click the link to open the runbook in the Runbook Editor.

• Description — An informative summary of what the associated runbook will do in response to the trigger.

• Last Updated By — The user who modified this trigger/runbook mapping most recently.

• Last Updated On — The timestamp for when this trigger/runbook mapping was modified most recently.

• Enable Automation — Execute the mapped runbook in response to the trigger. This is enabled by default; disable it only if you do not want a runbook to execute in response to the trigger.
  See the description of the Allow Automation control on the Runbooks page for details of enabling a runbook to be mappable to a trigger.

• ... — Choose from:

  • Edit — Open the Edit an Automation wizard to change the automation definition.

  • Duplicate — Copy this automation definition.

  • Delete — Remove this automation definition.

  • Change Order — Specify this automation's precedence for the trigger type.

  • Open Runbook — Open the currently mapped runbook in the Runbook Editor.