Define who is responsible for each day of the week and how alerts escalate through your team when a monitor goes down.
When a monitor goes down at 3 AM, you need the right person paged — not everyone, and not the wrong person. On-call scheduling lets you define who is responsible for each day of the week and set up automatic escalation steps so that if the first person does not respond, the alert moves up the chain.
On-call scheduling works at the project level. Every monitor in a project automatically benefits from the project's on-call schedule and escalation policy — there is no per-monitor assignment required.
When any monitor in a project triggers an incident, the following sequence runs:
Standard alert channels (email, SMS, Slack, etc.) fire immediately.
If the project has an escalation policy, step 1 is scheduled to fire after its configured delay (e.g. 5 minutes).
Monitorion looks up who is on-call today (checking date overrides first, then the weekly schedule) and pages them via the configured channels.
If the incident is not acknowledged before step 2's delay, step 2 fires. Escalation stops as soon as the incident is acknowledged or resolved.
The weekly schedule assigns a team member to each day of the week. Whoever is assigned for today is the person escalation step 1 (or any step targeting “on-call person”) will page.
Europe/Prague, America/New_York, UTC). Monitorion defaults to UTC if an invalid timezone is entered.Date overrides let you swap who is on-call for a specific date — useful for holidays, vacations, or coverage swaps. An override for a date takes priority over the weekly schedule.
An escalation policy is a sequence of paging steps. Each step defines how long to wait, who to page, and through which channels.
| Target type | Who gets paged |
|---|---|
| On-call person | Whoever is assigned for today in the weekly schedule (or date override). No one is paged if today has no assignment. |
| Specific team member | A fixed person — useful for a manager or backup who should always be in the loop. |
| Everyone | All project owners, admins, and members. Viewers are excluded. |
Understanding exactly when each step fires helps you configure delays correctly.
Acknowledging an incident tells your team that someone is aware and investigating. It also stops further escalation steps from firing.
| Requirement | Detail |
|---|---|
| Plan | All plans — on-call scheduling is available at no extra cost |
| Setup permission | Project owner or admin only |
| Acknowledge permission | Project owner, admin, or member (not viewer) |
| Context | Monitors must be inside a project (not standalone) |
| Team members | On-call assignments must be valid project members |
Go to your project settings and open the On-Call tab to get started.