Set Incident Priority

Assign the priority A classification that indicates the importance or urgency of an incident, used to prioritize investigation and remediation efforts. of an incident based on the execution of logic A runbook node category that adds conditions to branch the runbook, enabling conditional execution paths based on data and context. in a preceding connected Decision Branch node.

The resulting 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. priority is shown on the Incidents page and is included in the summarized incident information shown on the Impact Dashboard.

You can have multiple Set Incident Priority nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. per 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., with each one assigning the priority resulting from a preceding connected decision branch.

Properties

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

Set Priority To: Choose Critical (the default), High, Moderate, or Low.

Reason: Type in the text that you want to appear in the Priority Reasons view if this node is executed. You can embed variables in the text.

Runbook Compatibility

Incident