Maintenance windows: quiet alerts during planned work

A maintenance window quiets monitor alerts during planned work — a deploy, a database migration, a weekly restart. During a window every monitor it covers is still judged and recorded, so the history stays complete, but no notification is sent and no incident opens.

Open Monitors → Maintenance → New window.

What a window covers#

When#

• Once — a start time up to 366 days ahead.

• Every week — one or more weekdays and a start time.

Each window lasts 5 to 1440 minutes (24 hours). Times follow the time zone you pick (IANA, for example Europe/Berlin), daylight saving included: a weekly window at 02:00 stays at 02:00 local time across the change. On the night a clock jumps forward, a start inside the missing hour begins at the same offset as before the change; Belvador and the database apply the same rule, so the form preview shows exactly when it will start.

A workspace has up to 50 windows on the default plan. The optional reason (up to 200 characters) is shown to your team only and never sent in alerts.

What happens to an alert#

A problem that starts inside a window is still recorded on the monitor (with its counts) and marked as suppressed by that window. Nothing goes to Telegram, Slack, email or webhooks for it. If the problem is still there when the window ends, the monitor stays failing and normal alerting resumes for new problems.

Every create, change and delete is written to the audit log. The same windows can be managed with POST /v1/maintenance-windows and the MCP configuration tool.