Use maintenance window data
- Latest Dynatrace
- How-to guide
- 4-min read
- Preview
While a maintenance window is active, the maintenance metadata it adds to telemetry, problems, and events lets you filter views, refine automation, and audit what happened during planned work. This page covers three common tasks:
- Triage problems detected during maintenance.
- Configure problem-triggered workflows to skip maintenance periods.
- Query maintenance data directly with DQL.
Triage problems in 
Problems
During maintenance, Dynatrace still creates alerts and groups them into problems. Problem records include maintenance metadata (maintenance.is_under_maintenance=true) so you can find and manage them in Problems.
Recording problems during maintenance is useful because:
- They create a reliable record of what failed and when, which helps verify the scope of the change.
- They let you verify that you've resolved open issues before the window closes, so they don't surface as incidents later.
- They simplify audits and compliance reporting by showing issues that occurred during planned work.
Review issues
- Open Problems.
- In the filter field, start typing Under maintenance to show only problems detected under a maintenance window.
- Select the Under maintenance filter option.
- Select
=Equals andtrue. - Review each problem to confirm whether the issue is expected.
- Before the maintenance window closes, ensure all problems attributed to the planned maintenance are resolved.
Skip problem-triggered workflows during maintenance
To avoid sending notifications or triggering automations for problems that occur under a maintenance window, add a maintenance filter to the workflow's problem trigger.
-
Go to
Workflows. -
Select the workflow.
-
Select the Davis problem trigger.
-
In the Additional custom filter query field, add:
maintenance.is_under_maintenance != true -
Save the workflow.
The workflow now triggers only for problems that didn't occur during a maintenance window.
Query maintenance data with DQL
Query maintenance events and enriched telemetry directly in Grail with DQL to gather data for custom dashboards, availability reports, and audits.
List recurring window executions
View all executions from a recurring maintenance window:
fetch dt.maintenance.windows| filter dt.settings.object_id == "<MAINTENANCE_WINDOW_OBJECT_ID>"| sort timestamp desc
Find problems that occurred under maintenance
fetch dt.davis.problems| filter maintenance.is_under_maintenance == true
Find alerts that occurred under maintenance
fetch dt.davis.events| filter maintenance.is_under_maintenance == true
Find hosts currently under maintenance
timeseries avg_availability = avg(dt.host.maintenance), by:{host.name}, filter: maintenance.is_under_maintenance == true| summarize by:{host.name}, sum(1)
Calculate host availability
timeseries {m1 = sum(dt.host.availability, rollup: sum, default:0, filter: availability.state == "up"),mw = avg(dt.host.maintenance, filter: maintenance.is_under_maintenance, default:0)},by: {dt.smartscape.host},union: true,nonempty: true| fieldsAdd availabilityTS = if(mw[] == 0.0, m1[], else: toLong(interval) / 60000000000)