Hi,
There are several different methods of connecting nagios to ganglia in our
github repo:
* https://github.com/ganglia/ganglia-web/tree/master/nagios
* https://github.com/ganglia/ganglia-nagios-bridge
* https://github.com/ganglia/ganglia_contrib/tree/master/nagios
and I'm about to add a fourth, moving
https://bitbucket.org/maplebed/ganglios into github instead of bitbucket
(it wants to join its brethren).
What would you all think of reorganizing the repo a bit to concentrate
these things? Understandably the ganglia-web one can't be moved if it is to
remain part of the web installation, though a pointer to it could be
included in a centralized nagios-ganglia integration area.
Does this deserve a top level repo, or does it belong in the
ganglia-contrib repo? I lean towards making a 'nagios-integration' repo
since it is clearly something that is often done and has several different
methods. The argument for including it in ganglia-contrib could be made
pretty easily though.
Cheers,
-ben
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
