How to Schedule Maintenance Windows and Suppress Monitoring Alerts

Every service needs maintenance — deployments, database migrations, infrastructure updates, certificate rotations. Without a maintenance window, your monitoring tool will detect the planned downtime and fire alerts to your entire team. At 2 AM. On a Saturday.

What Maintenance Windows Do

A maintenance window tells Monitorion: "this service will be intentionally down between time X and time Y — do not create incidents or send alerts during this period." Checks still run (so you can see the actual downtime duration later), but no alerts fire and no incidents are opened.

Setting Up a Maintenance Window

1. Go to Maintenance in the sidebar
2. Click Schedule Maintenance
3. Enter a name (e.g., "Database migration v2.5")
4. Set the start and end time
5. Select which monitors to suppress — you can choose specific monitors or all monitors in a project
6. Click Create

The maintenance window appears on the calendar view and in the list view. Active maintenance windows show a green badge. When the window expires, monitoring resumes automatically — no manual action needed.

Best Practices

• Set windows slightly longer than expected — if your migration takes 30 minutes, set a 45-minute window. You can always end it early.
• Include dependent services — if you are migrating a database, suppress monitors for all services that depend on it.
• Communicate to stakeholders — use your public status page to notify customers about planned maintenance.
• Review completed windows — after maintenance, check the check history to verify the service recovered within the expected timeframe.

Try Monitorion free — maintenance windows are available on all plans.