On Mon, 20 May 2013, Michael Friedrich wrote:
> disable notifications and event handlers globally on the secondary
> (icinga.cfg). and if you are planning to have some sort of failover
> scenario, make sure to re-enable them once the primary is failing.
This sort of behaviour can be automated on the "usual secondary"
(i.e. the "duplicate"/"backup) using an out-of-band check to look
at the "usual master" (the instance that normally handles alerting
and event-handlers) that has access to the Icinga command file and
can jam commands to enable notifications and event-handlers on the
secondary if the master becomes impaired. (If the secondary becomes
impaired, the master will pick that up anyway.)
Don't try this from inside Icinga on the secondary as the secondary
won't have event-handlers globally-enabled! Perform the out-of-band
check using cron or some other job-scheduler of your choice.
Cheers!
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:crfri...@rcn.com +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
