<tt>> [Nagios-users] Expiration of passive check results</tt> <tt>> > - Is it possible in NAGIOS, to let the result of a passive check , > 'expire' after a given time period ? > (this could be used for errors, which are considered less > important, and are being considered 'dead weight' for > the time being). > > I mean if I a get a CRITICAL (passive) test result, from outside, > I would like NAGIOS to start a timer, > and set the alert to OK after a give time. > Now 'external' workarounds such as cron jobs may apply, but I wonder > wether this can be handled from within NAGIOS. </tt> <tt>Two things:</tt> <tt>- freshness</tt> <tt>- volatile services</tt> <tt>Freshness determines the timeperiod where a passive checkresult is</tt> <tt>considered "fresh" aka current. If the timeperiod is exceeded without</tt> <tt>receiving the next passive checkresult, then nagios issues an active</tt> <tt>check of that service. Of course you can define anything as active</tt> <tt>check you like. I use check_dummy to give me a WARNING "No passive</tt> <tt>data received!"</tt> <tt>Volatile services reset themselves to an OK state after each WARNING</tt> <tt>or CRITICAL. This is useful for things like snmp traps for example</tt> <tt>which notify of security impacts and you just want a mail for every</tt> <tt>checkresult that is considered a PROBLEM. Like a borderfirewall</tt> <tt>notifying you of an ongoing portscan or whatever. Volatile services</tt> <tt>are good for one-time notifications of events.</tt> <tt>Regards</tt> <tt> Sascha</tt> GFKL Financial Services AG Vorstand: Jürgen Baltes, Peter Blaschkowski Vorsitzender des Aufsichtsrats: Wilhelm Plumpe Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522