Hello, This service definition will, assuming a default interval_length, execute the check_debian_updates NRPE check every 5 minutes but only notify you every 24 hours in case of failure.
For this case, I'd suggest switching the values of notification_interval and check_interval (normal_check_interval is AFAIK v2, is that what you're running?) so that the check is executed once every 24 hours, but that you're notified every 5 minutes if the check returns non-OK. I don't know how your NRPE check is set up, but you might want to reconsider your max_check_attempts as well. If the check simply returns non-OK if there are updates available, you probably don't want to re-check for updates 10 times before notifying. I would also set flap_detection_enabled to 0 because you don't want Nagios to detect flapping with a check like this (otherwise the flap detection logic will consider the last 21 days of results) HTH, Martin Melin On Tue, Dec 29, 2009 at 12:38 PM, Brent Clark <[email protected]> wrote: > Hiya > > I was hoping someone would be kind to peer review my service check. > > I got a nrpe check to check that the debian packages on my servers are > up to date. I would like for this check to run once a day. > > This is what I was able to come up with. > > define service{ > use generic-service > hostgroup_name debian-packages > service_description Debian Packages > check_command check_nrpe!check_debian_updates > notification_interval 1440 > is_volatile 0 > check_period 24x7 > normal_check_interval 5 > retry_check_interval 1 > max_check_attempts 10 > notification_period 24x7 > } > > Is this correct, if not, would someone be kind enough to point me on the > correct path so that i can achieve this check. > > Kind Regards > Brent Clark > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > 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 > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ 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
