max_check_attempts ignores warnings?

[Kurt Yoder]

Hello

I would like my check_attempts and max_check_attempts to behave  
differently than it is now. Currently, assuming max_check_attempts is  
3, swap warning is 10%, and swap critical is 90%, I can have the  
following situation:

swap 5: ok
swap 15: warning (check_attempts 1)
swap 30: warning (check_attempts 2)
swap 45: warning (check_attempts 3: max_check_attempts is reached)
swap 95: critical (check_attempts 3: notification sent since  
max_check_attempts is reached)
swap 15: warning (check_attempts 3: max_check_attempts is still  
fulfilled)
swap 95: critical (check_attempts 3: notification sent since  
max_check_attempts is reached)
swap 95: critical (check_attempts 3: notification already sent)
swap 95: critical (check_attempts 3: notification already sent)
swap 95: critical (check_attempts 3: notification already sent)
swap 15: warning (check_attempts 3: max_check_attempts is reached)
swap 5: ok

I want it to do this instead:

swap 5: ok
swap 15: warning
swap 30: warning
swap 45: warning
swap 95: critical (check_attempts 1)
swap 15: warning
swap 95: critical (check_attempts 1)
swap 95: critical (check_attempts 2)
swap 95: critical (check_attempts 3: notification sent since  
max_check_attempts is reached)
swap 95: critical (check_attempts 3: notification already sent)
swap 15: warning
swap 5: ok

So I want check_attempts to only increment when I'm in critical  
state, *not* when I'm in warning state. Is it possible for me to  
configure nagios this way?

--
Kurt Yoder




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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