How maintenance windows work
When a maintenance window is active:- Alert suppression — No notifications are sent for the covered monitors (when
suppressAlertsis enabled) - Incident tagging — Any incidents created during the window get severity
MAINTENANCE - Monitoring continues — Checks still run, and results are still recorded for historical data
Creating a maintenance window
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
monitorId | UUID | No | Monitor to cover; omit for organization-wide |
startsAt | datetime | Yes | Scheduled start in ISO 8601 format |
endsAt | datetime | Yes | Scheduled end in ISO 8601 format |
reason | string | No | Human-readable description |
repeatRule | string | No | iCal RRULE for recurring windows (max 100 chars) |
suppressAlerts | boolean | No | Whether to suppress alerts (default: true) |
Omit
monitorId to create an organization-wide maintenance window that covers all monitors.Recurring maintenance
Use therepeatRule field with an iCal RRULE to schedule recurring windows:
| RRULE | Schedule |
|---|---|
FREQ=WEEKLY;BYDAY=TU | Every Tuesday |
FREQ=MONTHLY;BYMONTHDAY=1 | First day of each month |
FREQ=WEEKLY;BYDAY=SA;INTERVAL=2 | Every other Saturday |
Listing maintenance windows
| Filter | Returns |
|---|---|
active | Currently running maintenance windows |
upcoming | Scheduled future windows |
Updating a maintenance window
Deleting a maintenance window
Maintenance windows and alerting
Maintenance windows interact with the alert suppression system:- When
suppressAlertsistrue, all notification policies are bypassed for the covered monitors - When
suppressAlertsisfalse, incidents are still tagged asMAINTENANCEseverity but notifications still fire - Maintenance window suppression takes priority over notification policy rules
Next steps
Alert suppression
Other ways to suppress alerts — resource groups and more.
Incident policies
Configure trigger rules and recovery behavior.
Incidents guide
End-to-end guide for managing incidents.