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.
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.