Dynatrace provides two methods for defining maintenance windows
- Configuration API
- Dynatrace user interface
This page describes the UI-based approach. For the API reference, see Maintenance windows API.
Define a maintenance window
Each maintenance window you configure has a name and description that you can use to provide contextual information about the purpose of the maintenance window.
To define a maintenance window
- In the Dynatrace menu, go to Settings > Maintenance > Maintenance windows.
- Click Create maintenance window.
- Define a Name for the maintenance window.
- Provide a Description of the purpose of the maintenance window.
- From the Maintenance type drop list, select Planned or Unplanned.
- If the maintenance window is to recur on a regular schedule, use the drop lists to define a daily, weekly, or monthly recurring schedule.
- From the Problem detection and alerting drop list, specify the action that Dynatrace should take if a monitored component experiences a problem during a scheduled maintenance window:
- Detect problems and alert: Dynatrace will automatically detect and report all problems as usual and display a maintenance window icon on each problem that is detected during a maintenance window.
- Detect problems but don't alert: Dynatrace will detect problems but won’t send out alerts for them. Each problem will be listed on the Problems page with a maintenance window icon.
- Disable problem detection: Detection and alerting of problems is disabled. Problems that occur during scheduled maintenance windows will not be included on the Problems page and no alerts will be sent out.
- If needed, define the scope of the new maintenance window. Otherwise it applies for the entire environment.
Maintenance windows may be excluded from Synthetic Monitoring availability calculations by applying a global setting.
Define the scope of the maintenance window
By default, a maintenance window applies to your entire environment. The scope of a maintenance window can be narrowed down to select monitored entities while leaving everything else unaffected. The scope is defined by applying one or more entity filters. Each entity filter is evaluated independently.
Each entity filter applies to a certain type of monitored entity and contains one or more tags.
If multiple tags are specified, the entity must have all of them to be included in the scope of the maintenance window.
If no tags are specified, all entities of the specified type are included in the scope of the maintenance window.
To define a scope that includes entities that have any tag from a certain list, you need to create a separate entity filter for every tag from the list.