Set Structured Variable

Assign a value to a structured (complex) variable, in which the variable represents 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. that is summarized or aggregated from preceding nodesClosed Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. in the 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.. There are two types of structured variable:

  • Complex Summarized Data: Summarized output from a Data Query node, Decision Branch, or Transform node using definition from a variable. This must have a subtype to indicate what it represents, e.g. "ApplicationClosed An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies. Summary Data" or "Custom Summary Data". Available only for Runtime scope and Incident scope.

  • Complex Time Series Data: Any time series output from a Data Query node, Decision Branch, or Transform node using definition from a variable. This must have a subtype to indicate what it represents, e.g. "Application Time Series" or "Custom Time Series". Available only for Runtime scope and Incident scope.

Properties

Node Label: Type an informative name for the Set Structured Variable node. You can keep the system-provided default of "Set Structured Variable" if you wish.

Debug: Select Debug if you want to receive debug data when the node executes.

Variables to Set

Specify the variable. (Only one can be set per node.)

  • Scope: Choose the scope in which to set the variable's value. This is the environment, or set of conditions, within which the variable and its value are relevant.

    • Runtime Scope

    • Incident Scope

  • Variable Name: Choose an existing variable from the pulldown.

Runbook Compatibility

IncidentClosed 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., Lifecycle, On-Demand, External (Webhook), SubflowClosed 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.