Kaseya Community

Home » Discussion Forums » Monitoring - VSA » Monitor Sets - Services & Alarms

Learn more about how AuthAnvil can protect and enhance your Kaseya experience

Similar Posts

Suspend monitor sets & alarms during maintenance

by
on Jul 20, 2009

Monitor set not generating alarms & Kaseya support makes me cry :-(

by
on Jul 25, 2008

Suspending Alarms & Automatic Restarting of Services

by
on Oct 27, 2008

Monitor Sets & Access Rights

by
on Mar 14, 2008

Which monitor alarm set to trigger chkdsk?

by
on Jul 19, 2011
  • Not Answered
Details
  • 4 Replies
  • 0 Subscribers
  • Postedover 12 years ago

Monitor Sets - Services & Alarms

  • LegacyPoster
    Posted by
    on Dec 15, 2008 9:04 AM
    Hi,

    I have a few monitor sets that check to see if a service has stopped

    "Individually assigned: checks windows service for every 3 Minutes & restarted if stopped."

    Now this seems to work fine but it raises an alert when a service stops even if it was able to successfully restart the stopped service. Is there anyway I can make it so it alarms if it cant successfully start the service?

    Thanks

    Legacy Forum Name: Monitor Sets - Services & Alarms,
    Legacy Posted By Username: Joshua Lehman
  • LegacyPoster
    Posted by
    on Mar 16, 2009 11:53 PM
    Does anyone have a best practice on how to do this? Even if you put in a retry of 3 times every 5 minutes and a re-arm of 12 hours. You will only get notified once. No matter if the service was restarted or not. How about an alert that it could not restart a service? Is that possible to do?

    Legacy Forum Name: Monitor Sets,
    Legacy Posted By Username: ddenhoed
  • LegacyPoster
    Posted by
    on Mar 20, 2009 12:46 AM
    I wouldn't set the rearm for 12 hours.
    I just set one up for exchange:

    Set retry to 3, Interval to 3 minutes, and Rearm to 10 minutes.
    Applied the alarm to my exchange server with an email notification.

    If the service goes down, The service will be started 3 times, the last occuring at the 6 minutes mark. If after another 4 minutes, at the 10 minute mark, the service is still not running, another email will be sent that is down.

    The only down side to this is once I have automatic ticket creation up and running, i don't want a ticket made every ten minutes a service is down. The emails i am ok with though, it's better to have too much info than not enough.

    Legacy Forum Name: Monitor Sets,
    Legacy Posted By Username: boostmr2
  • LegacyPoster
    Posted by
    on Mar 20, 2009 1:40 AM
    I wouldn't set the rearm for 12 hours.
    I just set one up for exchange:

    Set retry to 3, Interval to 3 minutes, and Rearm to 10 minutes.
    Applied the alarm to my exchange server with an email notification.

    If the service goes down, The service will be started 3 times, the last occuring at the 6 minutes mark. If after another 4 minutes, at the 10 minute mark, the service is still not running, another email will be sent that is down.

    The only down side to this is once I have automatic ticket creation up and running, i don't want a ticket made every ten minutes a service is down. The emails i am ok with though, it's better to have too much info than not enough.

    Legacy Forum Name: Monitor Sets,
    Legacy Posted By Username: boostmr2
  • LegacyPoster
    Posted by
    on Mar 20, 2009 7:03 AM
    I contacted Kaseya support about this... they said basically there is no way to have it alarm only if the monitor set fails to restart a service. So i guess we will have to put this down in the feature request category?

    Legacy Forum Name: Monitor Sets,
    Legacy Posted By Username: cricketts