Maintenance windows
A maintenance window tells Vantaj that downtime during a known period is expected. While a window is active, the monitors you select are still checked, but their status changes don't trigger alerts — so a planned deploy or database migration won't page your team.
Find it under Status → Maintenance.
What a window does
- Monitors keep running and their results are still recorded
- Status-change notifications are suppressed for the selected monitors for the duration of the window
- When the window ends, normal alerting resumes automatically
This keeps your uptime history honest while sparing you false alarms during planned work.
Creating a window
- Go to Maintenance and click New maintenance window
- Give it a title (e.g.
Database migration) and an optional description - Set the start and end date/time, and the timezone they're expressed in
- Choose which monitors the window applies to
- Optionally make it recurring
- Save
One-time vs recurring
| Type | Use it for |
|---|---|
| One-time | A single planned event — a migration, a cutover, a one-off deploy |
| Daily | Routine nightly work, e.g. a backup window |
| Weekly | A regular weekly maintenance slot |
| Monthly | Monthly patching or billing-cycle jobs |
For recurring windows you also set an until date so the schedule doesn't run forever. Each occurrence inherits the same duration and the same set of monitors.
Tips
- Set windows a little wider than the work itself to absorb overruns
- Scope the window to only the monitors affected by the work — unrelated monitors keep alerting normally
- Times are stored in UTC internally but you enter them in the timezone you pick, so daylight-saving shifts are handled for you