service monitor that turns critical after 24 hours of downtime
dear all, i am looking for a way to create a monitor simlar to a generic service monitor. but one that turns to critical only after the service has been down for 24 hours. I have been trying with eventlog heartbeats and other tricks but non seem to be realy working. Can anybody point me in the right direction? Kind regards, Marc
September 28th, 2010 1:17am

Hi Marc, You can try to do it with one monitor and one rule. Rule: Script-based. It will check for service state and write events to eventlog. One event for "service is running" and one for "service is not running". Monitor: Missing event detection. First event "service is not running" and second "service is running". If second event wasn't occur in 24 hours then alert.http://OpsMgr.ru/
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2010 7:25am

Hi, I just noticed that you have also posted this issue in System Center Essentials Forum and I replied: service monitor that turns critical after 24 hours http://social.technet.microsoft.com/Forums/en-US/systemcentermonitoring/thread/b94baedd-16c3-4624-875d-caeade2120e8 I also would like to know what this issue is about, System Center Essentials or System Center Operations Manager. Regarding this issue, I would like to suggest you try again referring to the following guide first: How to Create a Windows Services Unit Monitor in Operations Manager 2007 http://technet.microsoft.com/en-us/library/bb381240.aspx To monitor a service, I think you can also try to do this with a script referring to: Monitoring a service for State and StartMode http://blogs.technet.com/b/jimmyharper/archive/2008/08/10/monitoring-a-service-for-state-and-startmode.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
September 28th, 2010 8:45am

Hi Alexey, Thanks for your input, this was indeed the way I initialy tried to get this to work but it seemed that my error was in the "healty" trigger. this looked for the wrong event ID. so now its working and its set up as follows: rule: run every 15 minutes and check if service is running via vb script. output to eventlog only if service is running, else void. monitor: check for missing eventlog messages within last 24 hours. en go critical if no are found. Thanks for your help. Kind regards, Marco
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 12:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics