I have two maintenance windows setup with overlapping timeframes.
The first maintenance window is set for every Saturday starting at 16:00 and ending the next morning at 6:00am, Applies to entire environment, Detect Problems, but don't alert.
The second maintenance window is set for every Saturday starting at 16:00 and ending the next morning at 6:00am, Applies to specific tagged Processes (Tag:[Environment]business-scope: pricing-and-trading), Detect Problems and Alert.
I created the first maintenance window in an effort to quiet the "noise" during our company's standard maintenance windows, but we have one team that still want's to get alerts during the maintenance window, so I setup the second maintenance window in hopes that it would generate the specific alerts that the team asked for. I currently have 4 open Problem tickets (for the tagged Processes in maintenance window 2), but never received the alerts for it.
Can someone please tell me if this is expected behavior?
If so, does anyone know of a way to keep the standard maintenance window (without having to add dozens of tags) with no alerting, yet still get the desired alerts for the one development team?
Solved! Go to Solution.
Maintenance windows are evaluated independently from each other. This also means that is one of the windows does mark a problem as being under maintenance and to suppress alerts you wont get any alert, no matter what other windows you define during the same time.
The only way to achieve your requirement is to use different tags or MZs for your individual teams and then define separate scopes for both maintenance windows.