Events API

Maintenance windows

Schedule quiet time for planned work — everything is still recorded, but nobody gets woken up.

Upgrading a database on Saturday night? You know alerts will fire, and you don’t want them paging anyone. A maintenance window is scheduled quiet time: incidents still open and record everything, but the paging politely waits.

Nothing is thrown away. When the window ends, any incident that’s still unresolved starts paging normally. You get silence during planned work without ever losing the record of what happened.

Schedule one

1. Open Configuration → Maintenance.
2. In Schedule maintenance, fill in:
   • Name — e.g. Database upgrade.
   • Scope — one service, or All services.
   • Starts and Ends — in your local timezone (shown under the form).
   • Reason — optional, but future-you will thank present-you.
3. Decide about the “Allow explicitly requested critical-event overrides” checkbox (explained below — leaving it on is recommended).
4. Press Schedule maintenance.

Windows move through simple states: scheduled → active → completed. You can edit a scheduled window, and Cancel one at any point — if you cancel an active window, paused incidents resume paging within about a minute.

What responders see

An incident opened during maintenance is clearly labeled — “Paging paused for maintenance” with the exact time escalation resumes — in the console and the mobile app. Anyone looking knows the alarm isn’t broken; it’s deliberately on hold.

The emergency escape hatch

What if something truly serious breaks during your maintenance window — unrelated to the planned work?

If the window allows overrides (the checkbox above), a monitoring system can mark an event as too important to hold by sending "maintenance_override": true in the payload of a critical-severity event. That one event ignores the quiet time and pages immediately.

Both halves must agree: the window must allow overrides, and the event must be critical and explicitly ask. An ordinary warning can never barge through.

{
  "integration_key": "YOUR-INTEGRATION-KEY",
  "event_action": "trigger",
  "dedup_key": "primary-db/replication-broken",
  "payload": {
    "summary": "Replication to standby has stopped entirely",
    "source": "db-monitor",
    "severity": "critical",
    "maintenance_override": true
  }
}