locked
Notification if server state goes from healthy to critical RRS feed

  • Question

  • Hi,I'm currently running OpsMgr 2012 on a small windows network environment.

    Everything is working fine. But I can't seem to find a way to get a notification only when the server state goes from healthy to critical. I do get notifications if there are critical alerts generated. But I would like to just receive a message like "Server A health state is critical" and not the specific reason.

    Is there any way to do that in SCOM 2012?

    Regards,

    Jp

    Monday, May 14, 2012 8:57 AM

Answers

  • Entity Health monitors are just roll up monitors that don't generate alerts and hence won't fire emails \ notifications. And I really wouldn't advise setting an override for the entity health monitors to generate alerts.

    To the original poster - you also need to be careful with the way scom works with regards to rules and monitors. Monitoring in SCOM is a mix of rules and monitors. But rules don't have state. So you could have a critical alert in the console (that is generated by a rule) but the server state is healthy because rules don't affect server state. I would reccomend alerting on critical alerts and tuning alerting so that you critical alerts are actionable (set an override against the alert severity to change the severity of an alert).

    If you are using SCOM 2012, this means you are licensed for Orchestrator 2012 - if you really want, you can setup a workflow here that checks the health state of a server on a regular basis and sends an email listing all critical servers (or you can have an email per server).

    Another option if you just want to see a list of unhealthy servers is to configure a dashboard or use Savision LiveMaps. But again, be aware of the way rules and monitors affect state.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Monday, May 14, 2012 11:02 AM

All replies

  • Hi

    SCOM doesn't work this way - you can set up a notification subsciption for alerts of specific severity but not for health state changes to specific health state.

    If you wanted to do it for health states then you would need to check the monitors to make sure that they were alerting on critical state. Most will ... but not all and 3 state monitors will only alert once. So if they alert on healthy --> warning they will not alert again on warning --> critical. Without the alert, you won't get the notification. Also, note that monitors don't necessarily roll up to Server \ Computer ...

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Monday, May 14, 2012 9:05 AM
  • Try to create subscription with notification criteria: created by specific rules or monitors and then select monitor: entity health.

    Roger

    Monday, May 14, 2012 9:26 AM
  • Entity Health monitors are just roll up monitors that don't generate alerts and hence won't fire emails \ notifications. And I really wouldn't advise setting an override for the entity health monitors to generate alerts.

    To the original poster - you also need to be careful with the way scom works with regards to rules and monitors. Monitoring in SCOM is a mix of rules and monitors. But rules don't have state. So you could have a critical alert in the console (that is generated by a rule) but the server state is healthy because rules don't affect server state. I would reccomend alerting on critical alerts and tuning alerting so that you critical alerts are actionable (set an override against the alert severity to change the severity of an alert).

    If you are using SCOM 2012, this means you are licensed for Orchestrator 2012 - if you really want, you can setup a workflow here that checks the health state of a server on a regular basis and sends an email listing all critical servers (or you can have an email per server).

    Another option if you just want to see a list of unhealthy servers is to configure a dashboard or use Savision LiveMaps. But again, be aware of the way rules and monitors affect state.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Monday, May 14, 2012 11:02 AM
  • Thanks for your answer, We're currently not using Orchestrator, but we might in the future, so I'll keep that in mind.

    I'm gonna stick to fine tuning the alerts for now.

    Regards,

    Jp

    Monday, May 14, 2012 11:49 AM