Configuration
MaintenanceWindow Options
string
required
A name for the maintenance window that will be displayed in the Checkly dashboard and used for identification.Usage:Use cases: Window identification, dashboard display, maintenance tracking.
string[]
Tags that filter which checks are affected by this maintenance window. Checks with ANY of these tags will be paused during the maintenance period to avoid unnecessary alerts. Not needed when Use cases: Service targeting, environment isolation, maintenance scope control.
pauseAllChecks is true.Usage:Date
required
Start date and time for the maintenance window in UTC (ISO 8601 timestamp).Usage:Use cases: Scheduled downtime, emergency maintenance, recurring maintenance timing.
Date
required
End date and time for the maintenance window in UTC (ISO 8601 timestamp).Usage:Use cases: Maintenance duration control, downtime limitation, schedule coordination.
number
Repeat interval from the first occurrence. Used with Use cases: Regular maintenance scheduling, automated recurring downtime, consistent maintenance intervals.
repeatUnit to create recurring maintenance windows.Usage:string
Repeat strategy that defines the time unit for recurring maintenance windows (Examples:Use cases: Time-based recurrence patterns, maintenance scheduling consistency, automated repetition.
DAY | WEEK | MONTH).Usage:Date
When to stop repeating the maintenance window (ISO 8601 timestamp in UTC). If not specified, the maintenance window will repeat indefinitely.Usage:Use cases: Limited-time maintenance periods, project-based scheduling, planned end dates.
string
The named IANA time zone used to schedule recurring occurrences, for example Use cases: Maintenance tied to local business hours, recurring windows that must survive daylight-saving changes.
"America/New_York". Occurrences keep the same local time across daylight-saving changes; see Timezones and daylight saving. Editors suggest known zone names as you type.startsAt and endsAt stay absolute instants: the time zone does not reinterpret them, it only decides how later occurrences follow local time. UTC offsets such as "+05:00" or "Etc/GMT+5" are not accepted. Defaults to UTC.Usage:boolean
default:"false"
Pause every check in the account during the maintenance window, regardless of Use cases: Account-wide migrations, full platform downtime.
tags.Usage:string[]
Tags that filter which checks have their alerts silenced during the maintenance window. Silenced checks keep running and collecting data, but alert channels aren’t notified. Ignored when Use cases: Keep monitoring during expected degradation without noisy alerts.
silenceAllAlerts is true.Usage:boolean
default:"false"
Silence alerts for every check in the account during the maintenance window, regardless of Use cases: Account-wide alert silencing while monitoring continues.
silenceAlertsTags. Checks keep running.Usage:Examples
- Database Maintenance
- Weekly System Updates
- Emergency Maintenance
- Service-Specific Maintenance
Best Practices
Time Zones: Always use UTC timestamps for consistency across different time zones. Convert your local maintenance times to UTC.