We copy check results between systems for redundancy purposes. Rather than using an event handler, we use the Obsessive Compulsive functionality. In the nagios.cfg file, I set the following:
obsess_over_services=1 ocsp_command=send_to_backup_nagios_server obsess_over_hosts=1 ochp_command=send_to_backup_nagios_server The send_to_backup_nagios_server command then sends the results to the other server. This doesn't handle synchronizing the downtime or acknowledgments. We're not currently doing that, though there was a recent post where I think someone posted a script for parsing the logs and sending these to another server. Scott Greenman Software Developer Family History Department The Church of Jesus Christ of Latter-day Saints ________________________________________ From: Getchell, Kristoffer M [[email protected]] Sent: Wednesday, October 07, 2009 8:14 AM To: [email protected] Subject: [Nagios-users] Sharing Check Results between Systems At present we have two main machines rooms, with each machine room running an instance of Nagios 3.0.6 that monitors machines close by. This setup works well, however to get an overview of the entire network we need to check in two locations - not ideal. What we want is a way to share information between the Nagios systems. To achieve this we've developed some management tools to allow us to synchronise the configuration of both Nagios systems. As part of the synchronisation process, services/hosts are set to be actively checked by their closest Nagios system and passively monitored by all others. Again, this works well but, at present we've no useful way of pushing the results of active checks to the other Nagios systems. Furthermore if a problem is acknowledge (or downtime scheduled) on one Nagios system, this is not copied to the other machines. To address these issues I've thought of the following: 1) Setup event handlers which will be enabled on active checks and used to push results from the Nagios system performing the active checks to all other Nagios systems. 2) Setup a long running service that parses the Nagios log files on each host and replicates any events between systems. As far as I can tell a combination of options 1 and 2 would provide what we're looking for, but I'm concerned that I might be missing something. Has anyone else tried to develop a similar setup? If so, what approaches did you take? Cheers, Kris This email has been scanned for all viruses by the MessageLabs Email Security System. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list [email protected] 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 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list [email protected] 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
