Subflow Overview

Navigate to the Subflows Page:

1. Click the Launchpad button ⁝⁝⁝.

2. Click AI Ops > Automations.

3. In the Management page, click the Hamburger Icon, then click Subflows.

A subflow A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems. is a sequence of runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. that execute a discrete runbook activity and that can be saved as an independent reusable component for inclusion in other runbooks. This makes a subflow a convenient means of implementing a common runbook operation once and including it in different runbooks where it is useful. For example, you could create a subflow to acquire the top traffic generating applications An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies. in the network, and reuse that subflow in multiple runbooks in which that application data is meaningful.

This image shows a built-in Subflow node (Parse Aternity Service Desk Alert) used in an Incident A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. runbook:

Subflows can be used in any type of runbook (Incident, On-Demand, or Lifecycle), and a single subflow can be used interchangeably across multiple runbook types if the nodes it includes are valid for each of the types. The subflow is validated for the runbook type in the context of the nodes that precede it and follow it in the runbook definition.

Subflows have version numbers (major.minor) associated with them. When a subflow is used in a runbook, the Runbook Editor shows that subflow version in the subflow node configuration blade. Minor version changes take effect automatically in every runbook that uses the subflow; major version changes require you to update each runbook manually. For details, see Updating subflows to a new version.

Built-in subflows

Riverbed IQ Ops provides a number of subflows as part of the product. They are listed on the Subflows page, in the Built-In tab, with corresponding descriptions. To work with subflows (create, add to runbooks, configure inputs and outputs), see Working with Subflows.

Learn more about subflows

• Working with Subflows: Create subflows, add them to runbooks, and configure subflow inputs and outputs.

• Subflow use case examples: Example scenarios for using subflows.

• Editing subflows and versions: Edit subflow definitions, work with older versions, and use the Save Subflow dialog.

• Managing subflow definitions: Export, import, and delete subflows.

• Updating subflows to a new version: How minor and major version updates affect built-in subflows, custom subflows, and integrations.