tutorialon-callincident-managementescalation

On-Call Scheduling for Small Teams: Set It Up in 10 Minutes

M

Monitorion

Monitoring Insights

||6 min read
Share:

Every team that runs production infrastructure eventually faces the same problem: when something breaks at 2 AM, who gets woken up? Without a system, either everyone gets paged (alert fatigue), nobody gets paged (missed incidents), or the same person always gets paged (burnout). On-call scheduling solves this — but most solutions require a separate $50+/month PagerDuty or OpsGenie subscription. Monitorion includes on-call scheduling at no additional cost.

What On-Call Scheduling Does

On-call scheduling defines who is responsible for responding to incidents at any given time. Combined with escalation policies, it ensures that:

  • The right person is paged first (the on-call engineer)
  • If they do not acknowledge within a set time, the next person or the whole team is paged
  • Nobody stays on-call every day — responsibility rotates on a schedule you define

Setting Up Your Schedule in Monitorion

On-call scheduling in Monitorion is project-based. Navigate to your project → On-Call tab.

Step 1: Weekly Schedule

Assign a team member to each day of the week. For a two-person team alternating weekly:

  • Week A: Person A on Monday–Sunday
  • Week B: Person B on Monday–Sunday

You can also assign different people to different days. Some teams do weekdays/weekends splits. The schedule respects your configured timezone.

Step 2: Date Overrides

Life happens. When someone is on holiday, travelling, or unavailable, add a date override to reassign that specific day to another team member without changing the base schedule. Overrides take precedence over the weekly rotation for their specific dates (up to 90 overrides can be configured).

Step 3: Escalation Policy

Switch to the Escalation Policy tab. Add up to three escalation steps:

  1. Step 1: 5 minutes after incident → page the on-call person via email and SMS
  2. Step 2: 15 minutes after incident → if not acknowledged, phone call to the on-call person
  3. Step 3: 30 minutes after incident → page everyone on the team via all channels

Each step can target: the current on-call person, a specific team member, or everyone in the project. Each step can use any combination of alert channels: email, SMS, phone call, Slack, Discord, Teams.

How It Fires in Practice

When a monitor in your project detects an incident, Monitorion sends your standard alert first (via your configured alert channels). The escalation policy then kicks in as a separate layer: Step 1 fires after its configured delay, Step 2 fires after its delay if the incident is not acknowledged, and so on.

Acknowledging an incident (clicking the Acknowledge button on the monitor detail page) stops the escalation chain. The acknowledged incident is flagged with who responded and when, creating an audit trail for post-incident reviews.

A Real Example: Two-Person SaaS Team

Alex and Jordan run a SaaS product together. They set up weekly rotation — Alex is on-call in odd weeks, Jordan in even weeks.

Their escalation policy:

  • Step 1 (5 min): SMS to on-call person
  • Step 2 (15 min): Phone call to on-call person
  • Step 3 (30 min): Email + SMS to both Alex and Jordan

At 3 AM when their database goes down, Alex (this week's on-call) gets an SMS. If he is deeply asleep and misses it, 15 minutes later his phone rings. If he still does not respond (maybe his phone is off), Jordan is looped in at the 30-minute mark. The incident does not go unaddressed.

Who Can Set It Up

On-call schedules and escalation policies are configured by project owners and admins. Team members and viewers receive pages based on the schedule but cannot modify it.

On-call scheduling requires your team members to be added to the project. Invite them under Project Settings → Team.

No PagerDuty Required

PagerDuty's cheapest plan starts at $21 per user per month. For a two-person team, that is $42/month just for on-call scheduling — before you pay for your monitoring tool. Monitorion includes on-call scheduling as part of the Pro plan ($29/month for the whole team), covering both monitoring and incident response in one platform.

Set up your on-call schedule free — invite your team and configure your first escalation policy in under 10 minutes.

Share:

Enjoyed this post?

Get monitoring tips and product updates delivered to your inbox.


Related Posts