Skip to content

Maintenance Windows

Reduce noise and risk during planned work.

Scheduled Windows Suppression Rules Patch Pause Automation Pause Alert Control
4
Suppression targets
Hierarchical
Scope
Recurring
Scheduling
Change windows
Use case

Maintenance Windows define time-bounded operating periods where selected automated behaviors should be intentionally suppressed.

Suppression Controls

Depending on configuration, teams can suppress:

  • alert notifications
  • scheduled patch actions
  • automation triggers
  • scheduled scripts

This prevents planned change activity from being treated as unplanned incident noise.

Policy Alignment

Maintenance settings can be resolved through policy hierarchy, allowing consistent behavior across organizations, sites, and groups.

Operational Benefits

Maintenance windows reduce false escalations, lower operational noise, and prevent overlapping automations from conflicting with controlled change work.

Why Teams Use It

Any environment with regular patch cycles, migration windows, or scheduled maintenance benefits from explicit suppression boundaries.

Practical Rollout Pattern

Most teams start with broad maintenance windows at the organization level, then add narrower site or group windows for business-critical systems with stricter uptime requirements.

This layered model keeps maintenance behavior predictable while preserving flexibility for high-priority workloads.

Capabilities

Suppression Controls

Teams can suppress alert notifications, patch actions, automation triggers, and scheduled scripts during windows.

Policy Hierarchy Alignment

Maintenance settings resolve through policy hierarchy for consistent behavior across orgs, sites, and groups.

Recurring Window Scheduling

Windows support recurring definitions for regular patch cycles, migration windows, and planned change work.

Noise Reduction

Prevents planned change activity from being treated as unplanned incident noise, reducing false escalations.