Semi-newbie Question

[Simone Felici]

AFAIK if you have configured a service to check 3 times befor send any notification, than this 
option cannot be override:

http://nagios.sourceforge.net/docs/nagioscore/3/en/statetypes.html

The first two "non-ok" states are in SOFT-STATE based on the max_check_attempts. You could try with 
event_handlers but are most used to correct an issue instead to force a notification, but could fit. 
They could be trigged in SOFT-STATE too.

http://nagios.sourceforge.net/docs/nagioscore/3/en/eventhandlers.html

BTW this would not log correctly the 503 error as an HARD-STATE issue for report pruposes.
I would set up a new service. It's cleaner. It could be a wrap-up of the check_http script to handle 
only 503 errors.

Hope it helps!

Bye,

Simon





Il 21/04/2011 01:02, Todd Clemens ha scritto:
> Hi Everyone,
>
> We monitor our sites with a standard 3 of 3 failure triggers a notification configuration.  I would
> like to know if it's possible to alter this monitoring (which would be ideal) or or create a new
> monitor (which is not as ideal, but is still ok) so that if a 503 error is detected, it will
> immediately send a notification and not wait for the 3 of 3 failure.
>
> Thanks,
> Todd
>

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
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