Notifications and Event-Handlers

[Rob Blake]

On 3/30/07, Dinçer Kavraal <dkavraal at yahoo.com> wrote:
>
> It's not dumb. I once try it. Answer is: no!
> They are not fired.
>
> To whom it may concern:
> Q: Why should somebody try this?
> A: Sometimes notifications can not be controlled through escalations
> easily. So you'd like to close all escalations and allow some of them.
> That's why. Anyway, no way to do it. If you disable for a hostgroup (for
> instance) notifications, then escalations and other settings related are
> ommitted.



I believe that this statement is incorrect. I see no reason why having
enable_notifications=0 will disable any event handler functionality. While
event handler commands and notification commands are defined in the same
manner, they are executed in different contexts by Nagios. If enable
notifications is false, then Nagios will not attempt to execute the command
that defines a "notification method" for the contacts associated with a
service/host. However it will still execute the event handler commands
associated with the said services/hosts as long as event handling is
enabled.

Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070402/1009a76f/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- 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