Alerting for Windows Service Components that may not be installed

gerretwalczak

Scenario:

I have an Application Monitor Template with 10 Windows Service components applied to 3 Nodes. I then have a single Alert that triggers if the Application is Down.

• APP01 - Has 9 of 10 Windows Services installed on the OS.
• APP02 - Has 9 of 10 Windows Services installed on the OS.
• APP03 - Has all 10 Windows Services installed on the OS.
  
  

How can I adjust the configuration on either the Components, Application Monitor Template, or Alert so that the alert doesn't trigger on the Nodes (APP01 and APP02) which do not have the tenth Windows Service installed?

I've simplified this example to three Nodes, but I'm looking for a solution which will scale to 5,000 Nodes. It doesn't make sense to me that a Windows Service Component which is not present on the system causes the Component to be in a Down state versus a neutral state. Not Running doesn't work in this scenario because it would require manual override of the Application Monitor Template on thousands of Nodes in our environment.

Solution Goals:

• I can apply the same Application Monitor Template to all 3 Nodes
• For APP01 and APP02, the Alert will never fire for that missing 10th Windows Service and the Application will show Up.
• For APP03 when the installed 10th Windows Service is in a Down state, it causes the Component to be in a Down state, causing the Application to be in a Down state, causing the Alert to trigger properly.

mesverrum

Basically it can't be done the way you want.  You either use 1 template with lots of over rides, or you use two templates to cover two different scenarios.  Creating over rides is not too hard to do via code if you have a look at the database and just insert some rows where the [key] = '__IsDisabled' and the value = 'true'

If you don't want to mess with code you will most likely need 2 templates.