I want to know if a service restarts 3 times in one hour. Right now I can only find a way to do 3 times, ever, using max_check_attempts.
Better ? Dan -----Original Message----- From: Mark Elsen [mailto:[email protected]] Sent: Wednesday, December 22, 2010 1:12 PM To: Nagios Users List Subject: Re: [Nagios-users] max_check_attempts over time > We're looking at a service that has problems from time-to-time, and it gets > auto-restarted when needed (Windows). What I've been looking for is a way > to say that it needs 3 restarts ir order to go critical, but only within a 1 > hour time frame. Anyone come up with a way to do time frames like this? > > Your problem is fuzzy defined : e.g : 'needs-3-restarts to go critical' , this can be be multi-explained. What is the correct one ? M. ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
