We have a fullblown Dynatrace Saas running i production. Integrated with Servicenow via the app from the market place.
BUT due to a scheuled maintenance window for the mainframe team, we get alot of false problems raised in the servicemanagement systems. Which causes a bit of frustrations for the dispacthers, and service owners as their KPI's gets an impact.
So would it be posible, in the Problem Settings to put in a maintenance zone in order to finetune the problems raised during these service windows?
Solved! Go to Solution.
Yes that's a very good point, I have the maintenance window functionality on the roadmap for quite a while now. Maybe its time to push that feature a little more.
Thanks for the hint, I will contact you once there is something in place you can test.
Sounds great, and will really help in an enterprise operations. To add a wish should this be enabled on a service level. So you can ajust the "Anomaly detection" on relevant services.
Maybe on a more theoretical note. Should the Maintenance Window be managed in Dynatrace or the Operations Management tool? In some organisations a Change Request (and subsequent Change Approval Boards) should be logged directly to a CI. This would mean that I know e.g. which set of servers should be patched to a new Windows Service Pack during a specific Maintenance Window. For a few servers this should be easy to manage within Dynatrace. But if I have a 100 servers to patch, this might not be the best place to do it, and will constitute a lot of extra work for the Operations team.
Hi Wolfgang, Is there any updates on this functionality on SaaS model to setup a maintenance window wherein we wont see any alerts during that window?
I fear not so far, but I have it on my priority roadmap. Sorry for the delay.
Hi Wolfgang, can you give any indication as to when this functionality is going to be implemented.
We plan to release maintenance windows around Q3 this year.
Wow that was some large t�ping.. Sorry about that
Calendar year. We started to implement the rest service within this sprint but it will still take some time to apply the window to all parts of the product. What would be your primary use cases, except not alerting and to respect that periods within the Availability reports.
Finished and published finally 🙂 Its public within Dynatrace SaaS release, Dynatrace Managed following in 4 weeks.