Re: [Ganglia-general] Sending alert

[Dan Rich]

[EMAIL PROTECTED] wrote:

I'm not sure I agree with your conclusion.  Why couldn't
the nagios plugin connect to a gmond on one of the nodes
in each cluster and parse the XML.  It should also have
a timeout to go to another node, if the "primary" happens
to be down.

I see ganglia's purpose as to collect performance information,
not monitor services.  I think it makes more sense to keep these
functions separate.  However, I think writing nagios plugins
to utilize ganglia information makes sense.

--Shane

[EMAIL PROTECTED] said:

Sadly, Nagios doesn't play well with Ganglia. See my (ancient) posting
to the Beowulf list:

--
Dan Rich <[EMAIL PROTECTED]> |   http://www.employees.org/~drich/
                              |  "Step up to red alert!"  "Are you sure, sir?
                              |   It means changing the bulb in the sign..."
                              |          - Red Dwarf (BBC)

The idea above is pretty-much what I was considering. I already have my nagios server receiving multicast from my various clusters, so it's fairly trivial to write a perl script that connects to the appropriate gmond and downloads the XML. My biggest concern at this point is getting the XML for several hundred hosts without blowing the memory on the system. After all, perl and XML::Simple are rather loose in their memory usage.

signature.asc
Description: OpenPGP digital signature