Contents / Alerts & notifications
Alert grading & on-call routing
#Alert grading
Under System settings in the Alert grading & on-call routing section, assign sites to levels (e.g. Critical, Normal) and give each level its own channels and recipients:
- Critical sites → email + DingTalk + browser push, all on;
- Normal sites → email only.
Escalation rule: if an incident stays unresolved for more than escalate_minutes minutes, it's escalated and resent through the higher-level channels.
#On-call routing
It's not a fixed roster you fill in — it's computed:
- Enter on-call members — your members' emails in order;
- Set the rotation cycle (days per person) and the start date;
- The system computes today's duty from member order + cycle + start date, and alerts go to whoever is on.
Why it's computed
A hand-filled roster always runs out — the schedule ends at month-end, nobody extends it, and alerts quietly go to nobody. Computing from "order + cycle + start date" can never run out.
On-call members' email addresses need recipient verification too.
Related: Notification channels · Team members