none
SCOM monitor multiple windows services

    Question

  • Hi all

    I want to monitor some services on a Windows server.

    Do I need to create monitoring for each service and service through "Add Monitoring Wizard"?

    Or is there a way to monitor all services together in one monitor?

    thanks

    Wednesday, July 11, 2018 1:30 PM

Answers

  • There's a slight difference between these :

    Template will discover if the service exists on a specific group of servers and then monitor, but it creates a lot of unnecessary objects.

    Monitor will just create a monitor that will apply to every instance of the targeted class.

    Best way would be to create your own custom class with a discovery rule and then target a simple monitor to this class; once again please refer to the replies in the thread I linked previously

    Wednesday, July 11, 2018 5:22 PM
  • Hi,

    Please read this here and decide for yourself. In general I agree with CyrAz.

    SCOM BASIC SERVICE MONITOR VS. WINDOWS SERVICE TEMPLATE

    Hope this helps

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Thursday, July 12, 2018 4:39 AM
  • Which way to choose ??

    Authoring>Management Pack Templates>Windows Service

    Or

    Authoring>Managements Pack Objects>Monitor> create unit monitor....

    Valid question...

    Now it depends your requirements, if you want to store CPU, Memory consumption report or alert on it for this service then use "Authoring>Management Pack Templates>Windows Service"  this way since this will create a rule in back-end to store this data and can also trigger alert for CPU, Memory and service stop state as well.

    And if you are doing it this way then create a group of servers on which use to want to enable this alert and collection and target this group during creation monitor.

    And if you dont want to collect availability report as well CPU, Memory data then use "Authoring>Managements Pack Objects>Monitor> create unit monitor"  this way since it will only create a monitor to reflect heath and generate alert on bad health (when service goes down).

    Note:- Just create for all the severs, where you want to monitor this service and target this group to enable these monitors in bulk for all servers.

    Now call is yours what you and how you want :)   


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Thursday, July 12, 2018 4:52 AM

All replies

  • Hey,

    You need a separate monitor for every service.

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Wednesday, July 11, 2018 2:12 PM
  • Or see replies to this thread if you're willing to go a bit further than the wizard
    Wednesday, July 11, 2018 2:38 PM
  • Which way to choose ??

    Authoring>Management Pack Templates>Windows Service

    Or

    Authoring>Managements Pack Objects>Monitor> create unit monitor....

    Wednesday, July 11, 2018 3:40 PM
  • There's a slight difference between these :

    Template will discover if the service exists on a specific group of servers and then monitor, but it creates a lot of unnecessary objects.

    Monitor will just create a monitor that will apply to every instance of the targeted class.

    Best way would be to create your own custom class with a discovery rule and then target a simple monitor to this class; once again please refer to the replies in the thread I linked previously

    Wednesday, July 11, 2018 5:22 PM
  • Hi,

    Please read this here and decide for yourself. In general I agree with CyrAz.

    SCOM BASIC SERVICE MONITOR VS. WINDOWS SERVICE TEMPLATE

    Hope this helps

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Thursday, July 12, 2018 4:39 AM
  • Which way to choose ??

    Authoring>Management Pack Templates>Windows Service

    Or

    Authoring>Managements Pack Objects>Monitor> create unit monitor....

    Valid question...

    Now it depends your requirements, if you want to store CPU, Memory consumption report or alert on it for this service then use "Authoring>Management Pack Templates>Windows Service"  this way since this will create a rule in back-end to store this data and can also trigger alert for CPU, Memory and service stop state as well.

    And if you are doing it this way then create a group of servers on which use to want to enable this alert and collection and target this group during creation monitor.

    And if you dont want to collect availability report as well CPU, Memory data then use "Authoring>Managements Pack Objects>Monitor> create unit monitor"  this way since it will only create a monitor to reflect heath and generate alert on bad health (when service goes down).

    Note:- Just create for all the severs, where you want to monitor this service and target this group to enable these monitors in bulk for all servers.

    Now call is yours what you and how you want :)   


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Thursday, July 12, 2018 4:52 AM
  • Here is a simple example for your reference:

    Keep Up: How to configure SCOM to monitor the running state of services and restart them when they stop

    https://garvis.ca/2015/01/05/keep-up-how-to-configure-scom-to-monitor-the-running-state-of-services-and-restart-them-when-they-stop/


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, July 12, 2018 8:38 AM
    Moderator
  • thank you friends 
    Thursday, July 12, 2018 8:57 AM
  • Besides Sam suggestion on service monitor and Windows Service template monitor

    https://anaops.com/2018/04/12/scom-basic-service-monitor-vs-windows-service-template/

    1. You only want to monitor the availability of the service. You are not concerned about the amount of CPU memory it is consuming. In fact, this is the case most of the times. You’re mainly focused only on the up/down status of the service. And in case you’re worried about CPU and memory utilization being consumed, you do have special dedicated monitors for them anyway.
    2. As the Window Service template creates a lot of things along with the service availability monitoring (1 class, 3 monitors and 6 rules), if you don’t actually need them, they’re just unnecessary overhead for SCOM. Now imagine you creating (1+3+6) 10 objects in SCOM for EACH service out of which 9 are not being used, how much litter you have created in SCOM. Basic service monitor on the other hand only creates 1 object (the actual availability monitor).
    3. It is much more work to disable the Windows Service template monitor than the basic service monitor. As you can imagine, if you no longer want to monitor the service, you’ll have to disable all 10 objects related to this monitor as opposed to just one in basic service monitor.

    some advantage of windows Service Template monitor over service monitor

    • it will check whether windows service is exist on target machine. If this service is not present in target machine, it will not monitor it. 
    Roger
    Thursday, July 12, 2018 9:31 AM
  • Besides Sam suggestion on service monitor and Windows Service template monitor

    https://anaops.com/2018/04/12/scom-basic-service-monitor-vs-windows-service-template/

    1. You only want to monitor the availability of the service. You are not concerned about the amount of CPU memory it is consuming. In fact, this is the case most of the times. You’re mainly focused only on the up/down status of the service. And in case you’re worried about CPU and memory utilization being consumed, you do have special dedicated monitors for them anyway.
    2. As the Window Service template creates a lot of things along with the service availability monitoring (1 class, 3 monitors and 6 rules), if you don’t actually need them, they’re just unnecessary overhead for SCOM. Now imagine you creating (1+3+6) 10 objects in SCOM for EACH service out of which 9 are not being used, how much litter you have created in SCOM. Basic service monitor on the other hand only creates 1 object (the actual availability monitor).
    3. It is much more work to disable the Windows Service template monitor than the basic service monitor. As you can imagine, if you no longer want to monitor the service, you’ll have to disable all 10 objects related to this monitor as opposed to just one in basic service monitor.

    some advantage of windows Service Template monitor over service monitor

    • it will check whether windows service is exist on target machine. If this service is not present in target machine, it will not monitor it. 
    Roger

    Very elaborated, thanks for information.

    Can you please share information about these (1 class, 3 monitors and 6 rules) in some detail. 

    Basically Monitor and Rule 


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Thursday, July 12, 2018 10:17 AM
  • Gourav,

    That is copied from the blog I posted earlier, which is coincidentally also written by me ;)

    Go through it once.

    Cheers 


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Thursday, July 12, 2018 10:23 AM
  • Done reading, i know about 4 rules got 2 more.

    Many Thanks :)


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Thursday, July 12, 2018 1:43 PM