Vantaj

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.

app.vantaj.co/maintenance
Database upgradeOne-time

Upgrading primary Postgres cluster to v16

Sat, Jan 24 · 02:00–04:00 · 3 monitors

Weekly backupsWeekly

Storage array snapshot window

Every Mon · 01:00–01:30 · 1 monitor

CDN migrationOne-time

Cutover to new edge provider

Sun, Feb 8 · 22:00–23:00 · 5 monitors

Schedule window

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
  • If the window is linked to a status page, it's announced there automatically - see Scheduled maintenance

This keeps your uptime history honest while sparing you false alarms during planned work.

Creating a window

  1. Go to Maintenance and click New maintenance window
  2. Give it a title (e.g. Database migration) and an optional description
  3. Set the start and end date/time, and the timezone they're expressed in
  4. Choose which monitors the window applies to
  5. Optionally make it recurring
  6. Save

You can also create a window directly from a status page - see Scheduled maintenance.

Viewing and editing a window

Click any window in the list to open its detail page. From there you can:

  • See the Affected monitors list - every monitor covered by the window, with its live status
  • Click Edit to change the title, description, or the selected monitors
  • Cancel, restore, or delete individual occurrences for recurring windows
  • Link or unlink the window from your status pages, under "Show on status pages"

A window needs at least one monitor selected - otherwise it won't suppress any alerts or show a maintenance state anywhere.

One-time vs recurring

TypeUse it for
One-timeA single planned event - a migration, a cutover, a one-off deploy
DailyRoutine nightly work, e.g. a backup window
WeeklyA regular weekly maintenance slot
MonthlyMonthly 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