Kibana alerting v2 maintenance windows
Maintenance windows are scheduled periods during which notifications are paused. Use them for planned deployments, infrastructure changes, or recurring maintenance that you know will trigger alerts.
During a maintenance window:
- Rules continue to execute and produce alert events.
- Alert lifecycle tracking continues (pending, active, recovering transitions still occur).
- Notifications through notification policies are suppressed.
- The dispatcher records suppressed outcomes for auditability.
When the maintenance window ends, notifications resume automatically.
- Navigate to the maintenance windows management area.
- Click Create maintenance window.
- Configure:
- Name and description.
- Schedule — start time, end time, and optional recurrence (daily, weekly, monthly).
- Scope — which rules or notification policies are affected.
Maintenance windows can be scoped by:
- Linked rules — suppress notifications for specific rules.
- Match conditions — suppress notifications for alerts matching specific attributes (for example,
env: production AND service: checkout). - Notification policies — suppress all notifications from specific policies.
The maintenance windows list shows all windows with:
- Window name and schedule.
- Status (active, scheduled, or expired).
- Linked rules and policies.
Notification policies can reference maintenance windows directly. From the notification policy form:
- Go to the Maintenance windows section.
- Select one or more maintenance windows to apply.
When a linked maintenance window is active, the policy's notifications are suppressed.
| Mechanism | Scope | Trigger | Recurrence |
|---|---|---|---|
| Maintenance window | Rule, policy, or attribute-based | Scheduled | Supports recurring schedules |
| Snooze | Per series | Manual (ad hoc) | One-time only |
Use maintenance windows for planned, recurring events. Use snooze for ad hoc suppression.