John, Naveen, I asked a similar question, basically about exporting the database into CSV format so that I can process it later with Excel or Access or similar. I was told that rrdtool is a good start. See the attached email.
Regards, Peter Managed Network Operations WorldCom c/o EDS Phoenix House Coronation Road Cressex Industrial Estate High Wycombe HP12 3TA Tel: 01494 607708 Fax: 01494 607999 -----Original Message----- From: Naveen Sivenandan [mailto:[EMAIL PROTECTED] Sent: 25 February 2003 06:30 To: 'John West' Cc: '[EMAIL PROTECTED]' Subject: [mrtg] Re: Longer-term history recording Hi,, I would be interested. Requests are often made to me , to look at utilization trends for more than a 12 month period etc. Regards Naveen -----Original Message----- From: John West [mailto:[EMAIL PROTECTED] Sent: 24 February 2003 09:44 To: [EMAIL PROTECTED] Subject: [mrtg] Longer-term history recording Please accept my apologies and a request for redirection if this is an often discussed topic, a FAQ, or if this is just outright the wrong forum for this sort of inquiry. I'm considering writing a companion piece of software for MRTG. What I have in mind is something that will capture the graphs that MRTG produces on a regular basis. These graphs would be stored, likely in a database, to provide a longer-term history than MRTG currently allows. Naturally, a corresponding web front-end would need to be written to allow for viewing the archived data. I'm thinking I'll even link the live data in as well, just to keep it seamless. I'm aware that recording the historical images in this manner undoes all of the effort of the round-robin database. However, it is a requirement of my environment. So, my questions to the list are: 1.) Is anyone else interested in this sort of thing? If there is enough interest, I could make the effort to generalize my approach. If I know that I can scratch someone else's itch, it makes it far more worth my while. 2.) Has someone else already done this? It'd save me the effort. ;) I haven't found any references to such a beast, but MRTG has been around long enough that I start to doubt that this is an original idea. 3.) Would you recommend saving the raw data or just the images? By making some rudimentary guesstimates, it would seem that storing the images would take far less disk space than the data itself. The downside, of course, is that you lose the ability to report on that data. If I'm writing this more generally, I can of course make this optional. Again, I apologize if I'm posting this in the wrong forum. Please let me know if there is somewhere better suited. Any constructive comments are most welcome. Thanks --John -- John West Software Consultant, Perl Monk Corporate Technologies, Inc. 781-273-4100 -- Attached file removed by Ecartis and put at URL below -- -- Type: application/pgp-signature -- Desc: This is a digitally signed message part -- Size: 190 bytes -- URL : http://www.ee.ethz.ch/~slist/pantomime/36-signature.asc -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Binary/unsupported file stripped by Ecartis -- -- Err : No filename to use for decode, file stripped. -- Type: message/rfc822 -- Desc: RE: [mrtg] Exporting mrtg database -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
