For SRE, platform and DevOps

On-call for SRE teams: your monitoring already knows. CallHeim makes sure a person does.

Repeats attach to one incident, the owning service’s escalation policy pages the right engineer, and the incident timeline records what happened.

Alert fatigue, not just alert volume

Noise rules you can explain in a postmortem.

You are the one who has to explain why a page did or did not arrive. These are the rules you would be explaining.

  • A repeat of the same alert attaches to the incident that is still open for it in the same service, with no new incident and no new page.
  • A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident.
  • Alerts from the same source and service whose titles share enough words (title similarity 0.6 or higher) group instead of paging twice, for as long as the first one is still open.
  • Maintenance windows suppress new alerts for a service, a team or the whole organization, and recovery events are exempt.

Published thresholds

CallHeim’s alert handling is rule-based and deterministic: given the same alert, settings and state, it makes the same decision.

A series that changes state 4 times in 600 seconds attaches to its open incident instead of re-paging. Title grouping can be switched off for your organization.

See the full noise reduction rules →

On-call that respects sleep

Fair on-call rotations

Pages per person is a poor measure of load, because being woken at 3 a.m. is not the same as being pinged at 3 p.m. The fatigue score weights them differently.

A published on-call fatigue score: 0.40 sleep-window interruptions, 0.30 volume, 0.20 off-hours, 0.10 severity, over a rolling 14 days. It is a heuristic over your own paging history, not a wellbeing measure.

The score can feed a fair-rotation suggestion that a person reviews and applies; it does not reorder a live rotation automatically.

See on-call scheduling →See how the fatigue score is calculated →

Fatigue weighting, published

  • 0.40

    Sleep-window interruptions (22:00–07:00 default)

  • 0.30

    Page volume

  • 0.20

    Off-hours pages

  • 0.10

    Severity pressure

Escalation and the record

Escalation that keeps going, and a timeline that stays accurate.

Escalation

  • An unanswered tier times out and the escalation moves to the next tier, ending at the fallback.
  • Escalation policies have up to 8 tiers, each paging a person, a team or a schedule, with per-tier timeouts from 1 to 240 minutes, optional repeats and a mandatory fallback. The whole chain must fit within 24 hours.
  • Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.
  • Acknowledging an incident stops the escalation.

See alerting and escalation policies →

Timeline and MTTA/MTTR

  • Lifecycle changes (acknowledge, resolve, close), comments, escalation steps and suppressions are written to the incident timeline as they happen, and the timeline has no edit or delete in the product.
  • MTTA and MTTR (mean, p50, p90) are computed from the incident’s own timestamps; reopened incidents are measured per response, merged duplicates are excluded and still-open incidents are flagged.

See the incident response workflow →

How you get paged

How pages reach your team.

Page

Incident pages go out by e-mail on every plan, each with a signed acknowledge link, and sent, delivered and bounced status is recorded on the incident. Pages can also go out by push, text message and phone call.

Acknowledge

Acknowledge an incident from the page e-mail or text through a signed, single-use link. It opens a confirmation page that names the incident, and it expires within 24 hours.

See every way a page can reach you →

CallHeim

Put a rule you can read between your alerts and your on-call.

Start a 14-day trial, connect one alert source and send yourself a test page.