That isnt completely accurate. rrdtool can take data at any interval, you just need to specify it when you create the rrd file. Personally, I get snmp data on 2 interfaces every 10 seconds and store them in two rrd files, and I have a php page that generates new graphs every time I view them (I migrated away from mrtg completely and just use rrd to store and graph). This was, the only consistent load on the box is from the snmp gathering (which is a local connection). The graph script runs only once every time the page is viewed, so the load is quite low there. however, I do agree that doing it all on the client would be better, but for a distributed viewing, a webpage makes a nice interface. jay ----- Original Message ----- From: "Stef Coene" <stef.coene@docum.org> To: <mingching.tiew@redtone.com>; <lartc@mailman.ds9a.nl> Sent: Monday, February 10, 2003 3:59 AM Subject: Re: [LARTC] API using cbq / tc ? > On Monday 10 February 2003 02:58, mingching.tiew@redtone.com wrote: > > Cool. As an MRTG idiot, I am going to ask this question, > > why can't it provide realtime stats ? You mean MRTG > > does not chart real time graphs ? > Mrtg is not designed for that. Mrtg uses rrdtool to generate the graphs. > You give the rrdtool each 5 minutes a number. This number is stored in a rrd > file. And you can generate a graph with the data in the rrd file. > > So it's for long-term graphing. If you want to do real time graphing, you > need new data each second. And you need to generate the graph on the client > side so you don't need to load each second a new graph from the server. >
