Runbook Node Compatibility Matrix
This topic demonstrates which runbook nodes
Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. can be used in which runbook types. Use the matrix when you need to confirm that a node is supported in an Incident, Lifecycle, On-Demand, External, or Subflow runbook, or when you need the node execution value for usage and licensing. For an introduction to runbook nodes, see Runbook Nodes. For categories and how to add nodes, see Runbook Node Categories and Assembling runbook nodes.
Runbook types in the matrix
The matrix has five runbook types as columns, plus an additional column for External runbooks that are created in Aternity (Embedded in Aternity).
-
Incident: Runbooks that execute automatically when a new incident is created.
-
Lifecycle: Runbooks that execute automatically when a triggering lifecycle event occurs on an incident.
-
External: Runbooks that trigger in response to a configured API call.
-
Aternity ISD: These runbooks are External runbooks but the editor shows a truncated set of nodes.
-
-
On-Demand: Runbooks that trigger as required (either on-demand, or as scheduled).
-
Subflow: Reusable chunks of automation that perform frequently used functions (e.g. open a ticket in an external system) and can be used to implement integrations with third-party systems.
The following table shows which nodes are compatible with which types of runbook. The Node Execution Value column shows the execution cost of each node. For monthly Node Execution counts, go to the Monitoring Usage page for the current and previous month.
| Node | Category | Incident | Lifecycle | External | Embedded in Aternity |
On-Demand | Subflow | Node Execution Value |
|---|---|---|---|---|---|---|---|---|
| Interface | Triggering Entity | ✓ | 1 | |||||
| Device[s] | Triggering Entity | ✓ | 1 | |||||
| Application[s]/Location[s] | Triggering Entity | ✓ | 1 | |||||
| Webhook | Triggering Entity | ✓ | ✓ | 1 | ||||
| Input | Triggering Entity | ✓ | 1 | |||||
| Runbook Completed | Triggers | ✓ | 1 | |||||
| Status Changed | Triggers | ✓ | 1 | |||||
| Note Added | Triggers | ✓ | 1 | |||||
| Note Updated | Triggers | ✓ | 1 | |||||
| Indicators Updated | Triggers | ✓ | 1 | |||||
| Ongoing State Changed | Triggers | ✓ | 1 | |||||
| Subflow Input | Subflow Input | ✓ | 0 | |||||
| Subflow Output | Subflow Output | ✓ | 0 | |||||
| Applications | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Devices (Traffic) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device Status | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (CPU Utilization) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (Memory Utilization) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (Disk Utilization) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (Availability) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Devices (Performance) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (Up Time) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Device (Configuration Changes) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Hosts | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Client Hosts | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Server Hosts | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Client-Server Pairs | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Locations | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Client Locations | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Server Locations | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Network Interfaces | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Interface Status | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Network Interfaces (Error Metrics) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Interfaces (Performance) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Protocols | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| DSCPs | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Client-Server Location Pairs | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Client-Server Pairs and Protoport | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| User Device (Deprecated) | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Data Store | Data Queries | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Aggregator | Functions | ✓ | ✓ | ✓ | ✓ | ✓ | 1 | |
| Transform | Functions | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 1 |
| GenAI | Functions | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Premium - 10 |
| Decision Branch | Logic | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 1 |
| Set Incident Priority | Impacts | ✓ | 1 | |||||
| Tag As Affected Applications | Impacts | ✓ | 1 | |||||
| Tag As Affected Locations | Impacts | ✓ | 1 | |||||
| Tag As Affected Users | Impacts | ✓ | 1 | |||||
| Add Insight | Impacts | ✓ | ✓ | ✓ | 1 | |||
| HTTP Request | Integrations | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 1 |
| Table | Visualizations | ✓ | ✓ | ✓ | ✓ | 0 | ||
| Pie Chart | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Bar Chart | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Timeseries Chart | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Bubble Chart | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Correlation Chart | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Cards | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Gauges | Visualizations | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Connection Graph | Visualizations | ✓ | ✓ | 1 | ||||
| Text | Visualizations | ✓ | ✓ | ✓ | ✓ | 0 | ||
| Set Primitive Variable | Variables | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 1 |
| Set Structured Variable | Variables | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 1 |
| Comment | Miscellaneous | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 0 |
| Note | Miscellaneous | ✓ | 0 | |||||
| Subflow | Subflows | ✓ | ✓ | ✓ | ✓ | ✓ |
see note below |
| Subflow Type | Node Execution Value |
|---|---|
| Customer-generated subflow | count of nodes executed inside the subflow |
| Riverbed-supplied built-in subflows | count of nodes executed inside the subflow |
|
Riverbed premium subflows |
(based on the specific subflow) |
| Premium: Aternity ISD Parse | 0 |
| Premium: OTel | Premium - 10 |