Notifications in a distributed setup

[Morris, Patrick]

> I'm interested in what people have designed for notifications 
> in a distributed setup. The official line is the master 
> server should handle all notifications. However, in a 
> geographically disbursed environment, there are two big 
> advantages of slave notifications:
> 
>    - the slave is autonomous - if you lose connection to the 
> master (whether scheduled or not), you will still get alerts
>    - pager notifications are routed locally, thus cost less
> 
> However, we're hitting problems because some notifications 
> should be handled from the master, such as RSS or helpdesk 
> integration. The only comms we allow from the slave to the 
> master is NSCA.
> 
> Has anyone solved this? Or is this why the docs recommend 
> master notifications?


In my typical setups, I'll have the slave servers check that nsca on the
master is working, and may add other checks to ensure the master's
operating correctly.  If one of those checks fail, I'll globally turn on
notifications on the slave server.  Otherwise, I'll have the master
handle all notifications.

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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