Nagios Support Forum

Hello there guys,

I've got a situation which is:

I'm monitoring a service every five minutes and the status information is sent to the DB every five minutes consequently.

The thing is: When service goes to critical, my application treats this as the service is out.

Basically what i wanted is that before the service goes to status CRITICAL, it holds on the OK status for a while and do the rechecks before goes to a CRITICAL state.

Lets say if Nagios detects that the service is CRITICAL it doesn't change the status, retrys 5 times in 5 minutes and if the service stills on CRITICAL state, then goes to CRITICAL.

Does anyone have an idea?

Well, if the check fails, it will go into a critical state. You can delay notifications and other actions with a retry value, and until that retry value is reached, the critical state is a soft type. This is how the logic works, and you would have to alter the core source to change it. You could wrap your check in another script that handles the logic before the check is reported to nagios. This would allow you to detect a failed state, save the info to a local file while returning ok. On the next check you would check the file for the state of the last check, and if it failed, and is still failing, then report a critical. This will require you to write a custom wrapper script for the check . . .

Thats how I have done. I wrote a custom script. Thanks for the help.