I have a task at hand :
Creating monitor to alert when a service is stopped.
We are using SCOM 2012
I checked and found various ways to do so http://www.bictt.com/blogs/bictt.php/2011/03/16/scom-monitoring-a-service-part1
My requirement is : there are like 100 such services on 100 different windows computers that i need to monitor.
The services are not common , so 2 computers have the same service , Maybe some service that i need to be monitored be on 2 computers but overall every service is unique.
What is my best option:
1.Create a basic unit monitor and target to Windows computer class ? Create is as disabled ? Override for just the machine that has it.
Will it clutter my Windows Server class health explorer . (How bad is that as per performance)
2.Create a Service monitor using Windows Service templates
Do i have to create 100 target groups , as i have to Target the monitor to specific computer only
Since template service monitor create discoveries , targets etc on its own (Am i going to clutter SCOM with a lot of those) 100
3.Do i create a attribute for each service , so as to extend the windows base class to discover the computer that has specific service (Using registry)
too much work is it and how good of an option is this.
4.MP Authoring ,Create new class discovery based on WMI / Registry to find computer and then target the monitor
What would you do in such a case.