How to stop IIS/WWW Publishing Service from raising Problems

[i_g]

Good afternoon,

We are having some frustrating problems during planned maintenance, where Dynatrace is raising problems and sending them through to SNOW for World Wide Web Publishing Service is in undesirable (stopped) state and Connectivity problem.

These are correct, as the services are stopped, however the server they're running on is in a maintenance window. The server is listed in the problem details as the Host, but the Problem Window has World Wide Web Publishing Service/IIS in the 'Impacted' column (see attached screenshot)

I've had a look but I can't see a way to selectively turn these alerts off. This is causing unneeded late night calls out for planned maintenance which is understandably, making the call recipients grumpy. Is there a way to shut down alerting during maintenance windows, or additionally through an API call? 

Thanks! 

[AntonPineiro]

Hi,

Some possible would be tagging processes and OS Services with autotagging rules.

And you can select that tag in your maintence window.

Best regards

[sujit_k_singh]

Hello @i_g 

The cleanest way to handle this is indeed through maintenance windows combined with tagging. If you need more flexibility, you can also manage maintenance windows via the Dynatrace API, which lets you programmatically set or adjust them before planned work. That’s useful if you have automated scripts that start/stop services and want alerting suppressed at the same time.

Thanks,

Tijust

[i_g]

Thanks everyone. Sorry for the delay, this got set aside over the Christmas break and I'm getting around to it now. I've managed to stop the IIS alerts using Process Monitor Tags and incorporating those into a maintenance window - but how do I stop World Wide Web Publishing Service? I can't see a way to tag by the service name at all, it's basically a crapshoot with Process Groups. The Problem has all of the information so I know Dynatrace has it, I just can't assign a tag to a Service? 
Edit - More to the point, why is Dynatrace alerting on a service running on a machine when that machine is in maintenance mode? 

[i_g · Accepted solution]

Anyway for anyone who has a similar problem, I managed to solve it by:

• Automatically tagging the IIS and IIS_default_app_pool process groups for each environment - I couldn't see an ability to limit this by host.
• Manually tagging the World Wide Web publishing service on each server from the GUI 
• Using the API, created a maintenance window for these tags. Probably could be added to the individual host maintenance window but my solution required a separate event.

I still don't see why there isn't an option to automatically tag an OS_Service, or why the process is so roundabout but that's neither here nor there at this point. Thanks for everyones help - I initially tried to avoid tagging but it was the way to go in the end.

ALSO seriously why is IIS/W3SVC raising alerts when the host it runs on is in a maintenance window? I feel like this might be a bug. But I've got a workaround at least.