Skip to content
Glowo
Esc
↑↓navigate↵open⌘Jpreview
On this page

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

Field Value Default
title 1–255 characters required
description up to 2000 characters none
startsAt ISO 8601 timestamp required
endsAt ISO 8601 timestamp required
timezone IANA timezone name, such as Europe/Paris UTC
recurring see below none
excludeFromUptime boolean true

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

Recurring windows

frequency Extra field
daily —
weekly dayOfWeek (0–6, Sunday is 0)
monthly dayOfMonth (1–31)
cron expression

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.

A window repeats on the day it first starts, at the same local time. So dayOfWeek and dayOfMonth are optional: when given, each must be the weekday or day of the month that startsAt falls on in the window’s timezone, and any other day is refused. A cron schedule needs an expression that names a time to come, read in the window’s timezone, and the timezone must be one Glowo can read. A schedule that could not repeat as written is refused when you save it, never stored to repeat nowhere.

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.

With it true, a check made during any occurrence of the window — its own dates, or any later repetition — does not count toward uptime: not in the uptime percentages, the daily uptime bars, a status page component’s status, the hourly statistics, or the check counts of the SLA report. Response times still cover every check, and the SLA report’s incident count still includes outages during maintenance.

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.

A window that repeats more than 2,500 times within the period being read cannot be left out exactly. The SLA report refuses such a period, so report a shorter one; the other views count that window’s checks.

Maintenance versus pausing

Maintenance window Pausing
Scheduled in advance yes no
Visible to users yes no
Checks keep running yes no
Right for planned work ad-hoc work, or a monitor you are fixing

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

Was this page helpful?