Thanks for the plug, but Opsview is not really suitable for this. We
have distributed monitoring out-of-the-box, but it requires the
permanent connection between slaves and the master which Nick says he
hasn't got.
If you will have temporary connections (that go up and down), we have
been thinking whether we can do "batched results from slaves", though
this is quite a big job as it requires changes to a lot of components
(Nagios, NSCA, NDOutils, and our datawarehouse). Let us know if you
fancy sponsoring this work.
Otherwise, why can't you just have notifications from the other
servers? Do you need to correlate with your central server?
Ton
On 28 Nov 2008, at 14:20, Assaf Flatto wrote:
Try looking at opsview , it is doing what you want with nagios as a
component in his setup.
http://www.opsview.org/
On Friday 28 November 2008 11:53:28 Nick Lunt wrote:
Hi folks
nagios 3.0.5 on RHEL 4u6.
We have nagios servers all over the uk and we want to get all alerts
from each nagios server to a central nagios server at our main
offices.
We do not have permanent network connectivity to the remote nagios
servers so using NSCA is not an option.
Has anyone any idea of how to overcome this problem ? I am thinking
of
getting the remote nagios servers to send email alerts to an
account on
the central nagios server then trying to get an alert generated
based on
the contents of the email, has anyone tried this before ?
Or does anyone have any better ideas for solving this problem ?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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