Maintenance Mode Manager for Dynatrace
Managing maintenance windows in Dynatrace is essential — but not always straightforward. While Dynatrace offers a built-in “maintenance window” feature, its configuration interface can be unintuitive and error-prone. Incorrect use may lead to incomplete suppression of alerts or unexpected data gaps, especially when applied by non-expert users.
The Maintenance Mode Manager App solves this by providing a clean, interactive interface tailored for real-world operational roles such as application owners, service managers, and servicedesk teams. Instead of wrestling with JSON payloads or complex selectors, users can easily:
- Select the entity that needs to be put in maintenance (various smart options)
- Define the maintenance window duration, scope and type
- Review and confirm changes in a guided side panel
This reduces human error, increases visibility, and empowers teams to safely perform maintenance without risk of alert noise or misconfigured windows.
Focused on practical simplicity — not full complexity
The Maintenance Mode Manager App is not intended to replace every advanced use-case that Dynatrace’s built-in maintenance configuration allows. Features like complex AND/OR conditions, recurring schedules, or multi-zone filters are deliberately not included in this version.
Instead, this app focuses on doing a few things very well – and making them safely accessible to day-to-day users. The result is a fast, intuitive tool that enables operational teams to perform their maintenance tasks with confidence, without needing deep Dynatrace expertise or risking misconfiguration.
For most real-world use cases – especially those driven by change management, planned deployments, or infrastructure patching – the app will be a welcome improvement in both clarity and reliability.
See also our blog: Smarter Maintenance in Dynatrace with the Maintenance Mode Manager
FAQ
No. This app focuses on simplicity for day-to-day operations. Recurring or complex schedules remain available in the native Dynatrace configuration.
Each Dynatrace environment supports up to 2,000 maintenance windows. This includes all windows, whether they are active, scheduled or expired; regardless whether created by UI or API.
If you try to create more than 2,000 maintenance windows, the system will not allow this until you delete one or more existing maintenance windows.
Once you reach 1800 defined maintenance windows in the system, the Maintenance Mode Manager app will show a warning to the user interface, once you reach 1950 defined windows, it will give you a “critical warning”, that you have to manually dismiss.
It may be tempting to delete expired windows quickly to “keep things tidy,” but in practice it’s often better to keep them for a while:
- Audit & reporting – Old windows provide context for why certain alerts or problems were suppressed at specific times.
- Troubleshooting – When investigating past incidents, knowing that a maintenance window was active can explain why alerts didn’t fire.
Dynatrace will still detect the issue, but if the impacted or root-cause entity is in maintenance, the problem will be annotated accordingly and alert-notification will be suppressed.
Once a maintenance window is defined, Dynatrace automatically excludes the configured time period from baseline calculations. This means that anomalies (such as higher response times) occurring during maintenance won’t distort the overall service and application baselines.
Parent and group relationships
In determining the scope of a maintenance window, Dynatrace considers entity parent and group relationships.
If a parent entity is scoped within a maintenance window, its immediate children are considered to be under maintenance as well. For example, if a maintenance window is configured for a host, all its disks are considered to be under maintenance as well. If a problem is raised on a disk, and the parent host is under maintenance, the affected child disk is considered to be under maintenance as well.
If an entity group is scoped within a maintenance window, its immediate members are considered to be under maintenance as well. For example, if a host group falls within a maintenance window, its member hosts are considered to be under maintenance as well. However, the child disks of the parent hosts are not considered to be under maintenance, unless, of course, the hosts are explicitly scoped within the maintenance window.
See: https://docs.dynatrace.com/docs/shortlink/maintenance-window-define#parent-and-group-relationships
Maintenance Mode Manager is designed for operational roles such as application owners, service managers, and service desk teams. It enables them to manage maintenance windows without needing full Dynatrace expertise.
The Dynatrace interface is powerful but complex. Our app provides a simplified, guided experience that helps operational teams avoid mistakes and set up safe maintenance windows in seconds.
Yes, this App is in active maintenance by IctCoreBiz, and will be updated with new functionality regularly. You can use the normal support channels to request specific functionality for new releases.