Hard State changes and notifications

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Sean McAvoy
> Sent: Thursday, November 15, 2007 4:29 PM
> To: Nagios Users Mailinglist
> Subject: [Nagios-users] Hard State changes and notifications
> 
> Hello,
> If a services is in an OK state then changes to Hard Warning state,
> is acknowledged and then enters a hard Critical state should a notice
> be sent assuming it passes all the filters (I am assuming that it be
> acknowledged is not a filter that would stop a notification)?

I would assume the opposite. An acknowledgement means that someone is
definitely aware of an issue with the host/service so no further
notifications are necessary.

The flow of check_service_notification_viability in base/notifications.c
seems to concur --

        /* has this problem already been acknowledged? */
        if(svc->problem_has_been_acknowledged==TRUE){
#ifdef DEBUG4
                printf("\tThis service problem has already been
acknowledged, so we won't send a notification out!\n");
#endif
                return ERROR;
                }

If I'm reading the code correctly, the check above is done for every
HARD state change.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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