- Open Routing rulesGo to Integrations → Routing rules.
- Create a ruleChoose "New rule", enter a Name and a Priority (lower numbers are evaluated first).
- Set conditionsPick Events, Categories, Monitors and tags, and active days and hours in the workspace time zone. Empty means everything.
- Choose destinationsSelect 1 to 20 shared destinations that should receive matching alerts.
- Add reminders (optional)Tick "Repeat until the incident is acknowledged" and set an interval of 15 to 1440 minutes.
- Save and previewChoose "Save rule", then use Routing preview to check which destinations an event would reach.
Routing rules decide which destinations receive each alert. Without rules, every verified, enabled shared destination receives every alert. Routing rules and repeat reminders are available on Pro and Team.
How rules are evaluated
Rules run in priority order, lowest number first (0 to 10,000). Every rule that matches adds its destinations. If a rule has Stop processing further rules when this one matches ticked, evaluation ends after it. If no rule matches, the fallback in Integrations → Settings applies.
Conditions
- Events: Monitor down (confirmed outage), Monitor recovered, and the SLO budget alerts (SLO error budget below 50% or 25%, SLO error budget exhausted, SLO fast burn). None selected means every routable event, including SLO budget alerts.
- Categories: none selected means every category. SLO budget alerts have no category, so a rule that picks categories never matches them.
- Monitors and tags: pick specific monitors or enter tags such as
checkout, api. Leave both empty to match every monitor. SLO budget alerts match through the SLO's monitor and its tags. - Active time (workspace time zone): pick weekdays and a From/Until time. No days means every day. Hours may cross midnight, for example 22:00 to 06:00.
Each rule sends to 1 to 20 shared destinations. Personal destinations are never used by rules; they are only paged through on-call escalation.
Routing SLO budget alerts
On Team, SLO budget alerts go through the same rules as outage alerts, so active hours and destinations apply. A rule with no event filter (and no category filter) also receives them. To send them somewhere specific, for example only to an email list during office hours, create a rule that selects just the three SLO events. Repeat reminders apply only to incidents, not to SLO alerts.
Repeat reminders
Tick Repeat until the incident is acknowledged and set Every (minutes) between 15 and 1,440. The rule's destinations then get a reminder at that interval until someone acknowledges the incident or the monitor recovers.
The fallback
In Integrations → Settings, choose what happens When no routing rule matches:
- Notify every verified, enabled shared destination (recommended).
- Notify nobody: the outage is recorded but not sent anywhere. Use this only when your rules cover every monitor.
Workspace time zone
The same page (and Settings → Workspace) sets the Workspace time zone, an IANA name such as Europe/Berlin. It is used only for the active days and hours of routing rules. Scheduled reports, recurring maintenance and on-call schedules each have their own time zone, and times on screen use your browser's time zone. In Routing preview, the At time is entered in your local time and evaluated against the rules in the workspace time zone.
Example setup
| Priority | Rule | Conditions | Send to |
|---|---|---|---|
| 10 | Critical at night | Tag critical, 22:00–07:00, down only | SMS, reminders every 15 min |
| 20 | Payments team | Tag checkout | Slack #payments |
| 100 | Everything | No conditions | Email, Slack #alerts |
Test before relying on it
Use Routing preview at the bottom of the Routing rules page. Pick an event, category, monitor and time, and choose Preview routing. It uses the same evaluator as the real dispatcher and lists which destinations would be notified and through which rule. Tick Include disabled rules to test a rule before you enable it.
If you move back to Free, rules are kept but ignored, and every verified, enabled shared destination receives each alert.
Frequently asked questions
What happens to alerts that match no rule?
The fallback in Integrations → Settings applies: either every verified, enabled shared destination is notified, or nobody is.
Which time zone do rule hours use?
The workspace time zone, set in Integrations → Settings or Settings → Workspace. It is used only for routing rules; reports, recurring maintenance and on-call schedules have their own time zones.
Do routing rules apply to SLO budget alerts?
Yes. Rules without an event filter match them too, and you can select the SLO events explicitly. Rules that pick categories never match SLO alerts, because SLO alerts have no category.
How often can reminders repeat?
Every 15 to 1,440 minutes, until the incident is acknowledged or the monitor recovers.