Using Variables in Visualization and Incident Priority Nodes

You can use runbookClosed 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 in VisualizationClosed A runbook node category that shows data in a chart, graph, table, or note, providing visual representation of analysis results in runbook output. nodesClosed Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. and Incident Priority nodes that outputClosed A document containing data sets generated by the execution of a runbook, including output of queries and reports from point products, as well as output of analysis or other runbook nodes. the results of runbook executions. This includes:

  • Titles in Visualization nodes

  • Notes in Visualization nodes

  • Incident Priority nodes

Visualization Titles

Note: Only primitive variables are allowed.

Type the variable in the Title field, e.g., "Data From {{runtime.MyCustomVariable}}"

Visualization Notes

Note: Structured time series variables are not allowed.

Type the variable directly in the Note field, e.g., "The result is {{runtime.MyCustomVariable}}"

Incident Priority Nodes

Note: Structured time series variables are not allowed.

Type the variable directly in the Reason field, e.g., "The result is {{runtime.MyCustomVariable}}"