You are correct, MRTG itself would be bad for this, but RRDTool and friends would be perfect for the job, and you can update in 30 second intervals or whatever. The thing I like about RRDTool is that I can easily take graph data from different devices, switches, even unrelated data (cpu vs packets for example) and plot them on the same graph. But this was done with my own custom program I wrote. Intermapper does not have to use RRDTool itself, but a similar working system would be exactly what we need.

The nice thing about my graphing system is that the data is already stored for everything, so AFTER the fact, I can go back and look at what happened, rather than saying "well, we're not graphing THAT port, but we can start graphing it now", and just hope the problem comes up again and we have data the next time around. The problem is that noone has released a "canned" solution (such as mine, which I'm sure many people have written the same thing). The only things I see out there are plain standard MRTG setups, or Cacti, which is RRD but still in only 5 minute intervals. I'm not sure if cacti will let you do intervals in the seconds timeframe, or if it will easily let you compare apples and oranges. I do think that alot of the data will have to be off-loaded to another box or something though, as the CPU and disk get hammered quite a bit.

At 10:11 AM 4/13/2006, you wrote:
I have to disagree on this point.  I already have MRTG, great tool for
trending but not good if I want to look at specifics of a day at a more
granular level.  The Intermapper graphs are great because I can view a day
and then drill down to a 30 second interval if I want. In addition, I can
create a graph on the fly, easy simple drag and drop, DONE.  See what is
going on, show customers that the problem IS NOT the network and delete it
after a day or so.

...

____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to