Incident Priority

When several incidents fire at once, responders need a fast, consistent way to know which one to tackle first. Without a shared classification scheme, "how bad is this" becomes a fresh judgment call every time, which slows triage and produces inconsistent responses across teams.

Incident Priority is a label — P1 through P5, most to least severe — that gets assigned to an incident to indicate its relative importance and impact. It's a separate property from Urgency, which only controls how a responder is notified (high or low); priority and urgency don't influence each other. Priority can be set manually when editing an incident, assigned automatically through Event Orchestration or automation rules based on conditions like the triggering service or alert content, or adjusted mid-incident if its impact grows or shrinks. It's available on Standard and Enterprise plans.

Because priority is tracked as its own field, teams can build dashboards, reporting, and SLAs around "how important was this incident" independent of how or whether someone got paged for it.

Learn More