Maintenance windows are one-time or recurring scheduled periods that mark planned maintenance and separate expected activity from unexpected issues in your observability data.
They tell Dynatrace when you expect non-standard operation, such as downtime, reduced performance, or high-traffic load tests.
Use maintenance windows to:
Suppress unwanted alert notifications during planned work.
Exclude planned disruptions from availability calculations so the uptime and baselines stay accurate.
Track current and historical maintenance windows for immediate and retrospective context.
Common use cases
Deployments, release windows, and rollbacks
Planned infrastructure or database maintenance and upgrades
Load, performance, or resilience testing that generates high traffic
Hardware, network, or cloud-provider maintenance
Limits
The following limits apply to maintenance windows:
You can create up to 100 upcoming maintenance window configurations.
Historical data is stored in Grail as start/end events and as enrichments on affected telemetry.
For more details on retention, see how to organize your data.
The maximum duration of a maintenance window is 7 days.