On-Call
On-call in Xitoring has two parts that work on top of your notification roles:
- On-call schedules decide who is on call at any moment, with rotations, overrides, holidays, cover requests and calendar subscriptions.
- Escalation policies notify more people, step by step, while nobody has acknowledged an incident.
Acknowledge and snooze are what stop those notifications. They are available on all plans.
How an incident reaches the on-call person
- An incident opens and the trigger's notification roles fire straight away.
- A role that has a schedule as a recipient notifies whoever is on call on that schedule at that moment.
- If the trigger, server or group has an escalation policy, its steps follow one after another.
- Someone acknowledges the incident and the repeats and escalation stop. The recovery notification still goes out.
Plans
On-call schedules and escalation policies are included in the Business plans. On other plans, creating a schedule or a policy is refused with a message to upgrade.
Who can manage them
| Who | See schedules and policies | Create, edit and delete them |
|---|---|---|
| Account owner | Yes | Yes |
| Team member with Full Access | Yes | Yes |
| Team member with the on-call permission | Yes | Yes |
| Any other team member | Yes | No |
Every team member can see who is on call, ask for cover and subscribe to a calendar. See Team Management for permissions.
See who is on call now
- API:
GET /api/v2/oncall/nowreturns, per schedule, the person on call, whether they come from a rotation or an override, and until when.on_callisnullwhen nobody is on call. - AI assistant: ask the MCP server, which has
who_is_on_call.