Maintenance Windows

Overview

A maintenance window is a scheduled time period during which sensor checks are paused. Use maintenance windows to prevent false alerts during planned operations — server updates, database migrations, network changes, or any other intervention that would temporarily disrupt monitored resources.

During a maintenance window, affected sensors are marked as "in maintenance" in the dashboard and no incidents are created for them.

You can manage maintenance windows from Monitoring → Maintenances in the Onagre dashboard.

Maintenance dashboard

The maintenances page displays:

• Active — Maintenance windows currently in progress.
• Scheduled — Upcoming maintenance windows.
• Past — Completed maintenance windows.

A calendar view shows all maintenance windows on a monthly grid, making it easy to visualize planned interventions. Below the calendar, a searchable table lists all windows with their name, scope, start/end times, and status.

Scheduling a maintenance

1. Navigate to Monitoring → Maintenances.
2. Click Schedule a maintenance.
3. Configure the window:

Timing

• Start date and time — When the maintenance begins.
• End date and time — When the maintenance ends.

Times are entered in your local timezone and automatically converted to UTC for consistent execution.

Identification

• Name — A short label describing the maintenance (e.g. "Database migration", "Server patching").
• Notes — Optional details about the planned work.

Scope

Choose which sensors are affected:

• All sensors — Every sensor in your organization is paused during the window.
• Specific agents — Only sensors linked to selected agents are paused. A visual grid lets you pick agents by clicking on them, with their online/offline status and sensor count displayed.

4. Save to schedule the maintenance.

Maintenance lifecycle

Each maintenance window goes through three states:

Actions

• Delete — Cancel a scheduled maintenance that has not started yet.
• Finish manually — End an in-progress maintenance early, restoring normal monitoring immediately.

What happens during a maintenance

When a maintenance window is active:

• Affected sensors are marked as "in maintenance" in the dashboard.
• Checks are paused — no measurements are collected.
• No incidents are created for affected sensors.
• No alerts are sent through your integrations.

When the window ends (either at the scheduled time or manually), monitoring resumes automatically. No manual restart is required.

Maintenance detail page

Click on a maintenance to view its full details:

• Name and status with color-coded badge.
• Notes describing the planned work.
• Start and end times in your local timezone.
• Number of sensors affected.
• Scope — Shows either "All sensors" or the list of selected agents.
• History timeline — An audit trail of all changes:
  • Created — who scheduled the maintenance and when.
  • Updated — any modifications to the window.
  • Finished manually — if someone ended it early.
  • Deleted — if the maintenance was cancelled.

Use cases

• Server updates — Schedule a window around OS or software upgrades to avoid false downtime alerts.
• Database migrations — Pause SQL sensors during schema changes.
• Network maintenance — Prevent Ping and Port alerts during planned network interventions.
• Deployments — Cover deployment windows where services restart temporarily.
• Infrastructure moves — Pause all monitoring during a datacenter migration.

Summary