distributed servers - how to tell which one executed a check?
Jason Martin
jhmartin at toger.us
Wed Apr 12 16:25:13 CEST 2006
On Tue, Apr 11, 2006 at 02:21:39PM -0700, Trask wrote:
> I haven't seen anything in the docs about this... I am hoping to have
> an indication somewhere of which distributed nagios server executed
> the last check.
How are the check results getting to the central server?
Assuming you are using the OCSP, couldn't you just modify that
script to prepend the hostname to the plugin output?
-Jason Martin
> A little background into my setup:
> - 4 nagios servers (all running 2.2 now)
> - nag1, nag2 and nag3 at each office/colo
> - nag4 is the central server receiving passive check info and serving
> as a fallback if one of the other 3 fail (and also importantly, the
> visual interface to all the checks).
>
> These are glued together with some homebrew scripts to ease management
> of the distributed setup. My goal is to be able to see which of these
> servers executed the last check.
>
> As a stop-gap measure I modified p1.pl to prepend the nagios server's
> hostname to the plugins output. This is an acceptable solution for
> the perl scripts, but that doesn't include any of the other (non-perl)
> plugins.
>
> Anyone accomplish this already or have an idea of how to do this?
>
>
> -------------------------------------------------------
> 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&kid0944&bid$1720&dat1642
> _______________________________________________
> 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
--
Brain over - Insert coin
This message is PGP/MIME signed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060412/7363db09/attachment.sig>
More information about the Users
mailing list