Notification after Acknowledgment

[Andre Kruger]

Hi
 
Thanks for that.
 
I just read how non-sticky acknowledgments work from 3.2.3. I think this solves my problem.
 
http://wiki.nagios.org/index.php/Acknowledgementlogic
 

Assuming you have a service with notifications enabled for all states with a max retry attempts of 1, these are the notifications you should get based on the following transitions: 
service in OK 
service goes into WARNING - notification sent 
non-sticky acknowledgement applied 
service goes into CRITICAL. Acknowledgement removed. Notification sent 
non-sticky acknowledgement applied 
service goes into WARNING. Acknowledgement removed. Notification sent 
non-sticky acknowledgement applied 
service goes into CRITICAL. Acknowledgement removed. Notification sent 
service goes into OK. Recovery notification sent 


>>> Jim Avery <jim at jimavery.me.uk> 2011/05/13 09:57 >>>
On 13 May 2011 08:34, Andre Kruger <Andre.Kruger at trw.com> wrote:
> Hi
>
> Can you guys please give me your input on how you handle the following
> situation.
>
> Lets take monitoring a disk as an example. For arguments sake lets say when
> the disk reaches 80% capacity I send out a warning and at 90% I send out a
> critical. There is also a Service Escalation configured to send out
> notifications when this service reaches critical.
>
> So at 80 percent I get my notification all is well. I then go ahead and
> acknowledge the event and in doing so Nagios will not send out any further
> notifications. Which according to the Nagios logic is correct.
>
> The problem is if the disk in the mean time reaches critical, 90% capacity,
> I won't get another notification. Not even the Service Escalation helps
> here, because the event has already been acknowledged.
>
> Do you guys have any suggestions on how this problem can be solved?
>
> Regards
> Andre


The way I sometimes use for prolonged issues like this is I will
acknowledge the alert, but then raise the warning and critical
thresholds in Nagios.  The problem with this approach is that Nagios
then reports the status as "OK" which might give a false impression to
other users.  It is also important to remember to reduce the warning
threshold back to its usual level once the issue is resolved.

For issues which might be fast-moving I would suggest that it is not
appropriate to acknowledge the issue unless you are in a postion
actively to manage it until resolution.

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
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


Please consider your environmental responsibility before printing this e-mail or any other document. Ask yourself whether you need a hard copy.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110513/229b2bf1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
-------------- next part --------------
_______________________________________________
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