Severity-based routing
Last updated 2026-06-14
Definition
Severity-based routing sends each alert to a different place depending on how serious it is. A critical drop can fire to Slack and email at once, while a low-priority flag quietly joins a digest. You set the rules once, so urgent problems interrupt you and minor ones wait, instead of every alert shouting equally.
How to do this in Quri
- Open your workspace notification settings and find severity routing.
- Map each severity level to the channels it should reach — critical to Slack plus email, say.
- Send lower-severity alerts to a digest so they batch instead of pinging you live.
- Save the rules; Quri then routes every new alert by its severity automatically.
Frequently asked
- Why route alerts by severity?
- So a real emergency reaches you the fastest way while routine flags stay quiet. Without it, a minor wobble interrupts you as loudly as a revenue collapse, and you start ignoring all of them.
- What happens if I do not set any routing rules?
- Alerts fan out to your default channels unchanged. Severity routing is opt-in — turn it on when you want critical and low-priority alerts to land in different places.