Route alert episodes by severity in the experimental alerting system

Use this page to send critical and non-critical alert episodes to different workflows by scoping one action policy per severity.

For example, you might page an on-call team for critical alert episodes while sending lower-severity alert episodes to a Slack channel for async review.

Each action policy evaluates alert episodes independently.

• An alert episode with severity: "critical" matches Action Policy A but not Action Policy B.
• An alert episode with severity: "high" matches Action Policy B but not Action Policy A.
• If an alert episode's severity changes mid-lifecycle, the action policies that match it change accordingly. For example, if an alert episode escalates from high to critical, Action Policy A starts matching and Action Policy B stops matching. Action Policy A fires because it has no prior notification record for that alert episode.

• Manage severity escalation notifications: Understand what happens when an alert episode that has already matched an action policy changes severity.
• Action policy reference: Look up match condition fields, grouping modes, and frequency options.
• Create and configure an action policy: Set up an action policy with match conditions.