In message <[EMAIL PROTECTED]>,
"Philip Hallstrom" writes:
>I've read through the docs and distributed, failover, and redundant
>monitoring, but those didn't seem to apply.
Part of them did. Reread the section(s) on sending passive events to
another nagios server.
>I'm wondering if two nagios instances can be set up to monitor the
>same hosts/services and have to agree with each other before sending a
>notification?
One way to do this is to set up the following:
On nagios 1 service A1 (no notifications)
On nagios 1 service A2 (passive update from server 2, not polled
from server 1, no notifications)
On nagios 2 service A2 (no notifications)
On nagios 2 service A1 (passive update from server 1, not polled
from server 2, no notifications)
On both nagios 1 and 2 create service B that does notify (and poll)
that uses check_cluster to require that both be in error condition to
generate an error notification.
Set up the passive services to have a freshness interval just a little
longer than the polling interval on the other server. This way loss of
the remote server is detected and causes the passive service to fail.
Also service B can use another script that you write to require
exactly the same service output etc or perform other correlation
requirements.
Send the passive service via ssh, nsca, carrier pigeon etc.
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users@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
