Using Variables in Visualization and Incident Priority Nodes

You can embed 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. variables A runbook node category that aggregates or transforms data forwarded from a preceding node, enabling data manipulation and analysis. in the text fields of Visualization A runbook node category that shows data in a chart, graph, table, or note, providing visual representation of analysis results in runbook output. nodes and in the Set Incident Priority node. When the runbook runs, the runbook replaces the variable with its current value. Titles, notes, and priority reasons can reflect data from the run (for example, a chart title that includes a metric value or a priority reason that cites a custom severity). That capability makes runbook output and incident prioritization easier to interpret and audit.

Variables are defined in the Variable Definition Editor and set elsewhere in the runbook (for example, in Set Primitive Variable or Set Structured Variable nodes). For an overview of variables and how to define and set them, see Variables Overview and Using User Defined Variables in Runbooks. This topic describes where and how you can use those variables in visualization and priority nodes.

Where variables are allowed

You can type variable references (for example, {{runtime.MyCustomVariable}}) in:

• Visualization nodes: The Title field and the Notes field. Visualization nodes include Table, Bar Chart, Time Series Chart, Pie Chart, Text, and other chart and card nodes. You add and configure them in the Runbook Editor. Their output appears in the Incident Details Runbook Analysis section.

• Set Incident Priority node: The Reason field. The reason appears in the Priority Reasons view when the node runs and helps document why the runbook set the incident priority.

Visualization titles

In the Title field of a visualization node, type the variable using double curly braces. For example: Data From {{runtime.MyCustomVariable}}. When the runbook runs, the runbook replaces {{runtime.MyCustomVariable}} with the variable's value.

Visualization notes

In the Notes field of a visualization node, type the variable in the same way. For example: The result is {{runtime.MyCustomVariable}}. Only primitive (and certain structured) variable types are supported. Time series data cannot be embedded in notes.

Set incident priority reason

In the Reason field of the Set Incident Priority node, type the variable so the reason reflects runbook data. For example: Priority set based on {{runtime.AlertSeverity}}. The value appears in the incident's Priority Reasons and helps explain why the runbook chose that priority.