Maintenance windows

Schedule planned work so alerts stay quiet, uptime stays fair, and users are told in advance.

A maintenance window tells Glowo that downtime is expected. Alerts are suppressed, the component shows UNDER_MAINTENANCE, and — by default — the time is excluded from uptime.

Fields

endsAt must be after startsAt — enforced both in the domain and by a database constraint.

Recurring windows

Set timezone for anything recurring. A window defined in UTC drifts by an hour relative to local working time when daylight saving changes, and will eventually cover the wrong part of your night.

Windows cannot overlap

Two maintenance windows on the same monitor may not overlap. This is enforced by a database exclusion constraint, not just by the UI, so it holds even for concurrent requests.

If a window is rejected, an existing one already covers part of that period — extend it rather than adding a second.

excludeFromUptime

Leave it true for genuine planned maintenance: you agreed the downtime in advance, and counting it against your SLA is not meaningful.

Set it false when you want the window only to suppress alerts while still counting the impact — useful when you are being held to an availability number that does not carve out maintenance.

Maintenance versus pausing

Because checks keep running during maintenance, you can see whether the work actually finished on time.