Maintenance Windows
Maintenance windows let you suppress alerts during planned downtime. When a maintenance window is active, incidents detected on the affected node(s) will not trigger notifications, preventing alert fatigue during expected traffic disruptions.
Creating a Maintenance Window
- Go to Maintenance in the sidebar.
- Click New Window.
- Fill in the form:
- Node: Select a specific node, or leave blank for all nodes (workspace-wide).
- Reason: A description of why the window is needed (required).
- Start time: When the window begins.
- End time: When the window ends (must be in the future, must be after start time).
- Suppress L7 alerts: Optionally suppress Layer 7 (HTTP) alerts during the window.
- Recurrence: Set to None, Daily, Weekly, or Monthly for recurring windows.
- Recurrence end date: For recurring windows, set when the recurrence should stop.
- Click Create.
Scope
| Scope | Behavior |
|---|---|
| Specific node | Only alerts for that node are suppressed. Other nodes continue to alert normally. |
| All nodes (workspace-wide) | Leave the Node field empty. Alerts for every node in the workspace are suppressed during the window. |
Alert Suppression During Maintenance
During an active maintenance window:
- The agent continues to monitor traffic and detect incidents normally.
- Incidents are still recorded in the dashboard.
- Notifications (Slack, Discord, PagerDuty, email, etc.) are suppressed for nodes covered by the window.
- If Suppress L7 is checked, Layer 7 alerts are also suppressed.
This means you will not lose visibility. All incidents are still logged, just not alerted on. After the window ends, normal alerting resumes automatically.
Ending a Window Early
If your maintenance finishes ahead of schedule, click End Now next to the active window. This immediately closes the window and resumes normal alerting.
Deleting a Window
Upcoming or past windows can be deleted from the maintenance page. Active windows should be ended first (using End Now) before deletion.
Recurring Windows
For regular maintenance schedules, set the Recurrence option:
| Recurrence | Behavior |
|---|---|
| None | One-time window only |
| Daily | Repeats every 24 hours at the same time |
| Weekly | Repeats every 7 days at the same time |
| Monthly | Repeats on the same day of each month |
Recurring windows automatically generate the next occurrence after the current one expires. You can set a Recurrence end date to stop the recurrence at a specific date.
The system checks for expired recurring windows on each page load and creates the next future occurrence if one does not already exist.
Window Views
The maintenance page organizes windows into three sections:
- Active Windows: Currently in effect. Shows node, reason, start time, countdown to end, and an End Now action.
- Upcoming Windows: Scheduled but not yet started.
- Past Windows: Last 10 completed windows for reference.
Permissions
Creating, ending, and deleting maintenance windows requires the Admin role or higher. All maintenance actions are recorded in the audit log.
FAQ
Do incidents still get created during maintenance?
Yes. The agent continues to detect and report incidents. Only the notifications are suppressed. You will see the incidents in the dashboard after the window ends.
Can I have multiple overlapping windows?
Yes. Multiple windows can be active simultaneously. If any active window covers a node, alerts for that node are suppressed.