nagios / cacti integration question

[Thomas Guyot-Sionnest]

On 20/07/07 10:28 PM, Thomas Guyot-Sionnest wrote:
> 
> There is no standard way but in my company we developed our own Perl
> daemon for gathering performance data from a Nagios pipe and caching it.
> A Cacti script connects to the daemon to get the data... You will need a
> good understanding of Cacti (to create the new templates and data input)
> and a bit of patience.
> 
> The daemon doesn't have any configuration (yet) so all variables are
> hard-coded in the code. For example to change the data retention timeout
>  (which is 120 seconds right now since our Nagios checks every minute
> and our Cacti is patched to poll at the same interval) you will have to
> change it in the cache_cleanup sub.
> 
> The latest daemon code with some bugfixes is available here:
> 
> http://www.nagiosexchange.org/Misc.36.0.html?&tx_netnagext_pi1%5Bp_view%5D=972
> 
> And the setup instructions are here:
> 
> http://www.control-alt-del.org/code/NPDaemon/

Oh, one more thing I forgot to mention, by default the daemon listens on
the localhost only so this works only if Cacti is running on the same
server. If you want to run it trough the network you will have to change
NPDaemon; at line 44 you have:

LocalAddr => '127.0.0.1',

Change it to the IP of the interface you want it to listen on, or
'0.0.0.0' to listen on all interfaces. There is to authentication so you
 may want to run it only on a secured network or with a local firewall
restricting access.

The cacti script has to be modified as well to connect to the right IP.

Thomas

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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