Re: Monitoring multiple devices with MRTG

The recommended Best Practice is to have a separate cfg file for each device, for ease of management and to air your chosen web frontend.

You can then link them together using a 'master' CFG file, that uses the Include: directive to include all the components together, and run MRTG (possibly in daemon mode) against that master file.

When you make changes to your cfg files, you can touch the master.cfg, which will cause MRTG to re-read it in if necessary.

The latest MRTG will support wildcard-based Include directives, which makes things much easier.

We monitor over 40,000 metrics in our MRTG setup; we use a distributed Gearman-based scheduler, and the MRTG instances NFS mount the cfg filesystem and use a network-based rrdcached to hold the databases centrally (note - this requires rrdtool 1.4trunk or 1.5beta for MRTG to be able to create rrd files over rrdcached).  Then a single centralised Routers2 instance reads the rrd files.

Steve

Steve

Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
[email protected]<mailto:[email protected]>
Ph: +64 9 373 7599 ext 86487

________________________________
From: mrtg [[email protected]] on behalf of Rick Silacci [[email protected]]
Sent: Saturday, 14 March 2015 7:48 a.m.
To: [email protected]
Subject: [mrtg] Monitoring multiple devices with MRTG

Is there a way to do this without making a separate cfg file?  I have 2000 devices I need to monitor.

Thanks

Rick Silacci
Velociter Wireless
209.838.1221 x107
[VWTwitter]

_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg