The intention is not to replace the .log/.rrd backend for MRTG with SQL, but to create a granular archive for billing purposes. In this environment there are hundreds/thousands of interfaces being monitored by MRTG. Only 1/2 interfaces per switch are being used for billing, and only those interfaces are being logged to SQL. By default mrtgsql will not dump all of the data into SQL, you have to specify which interfaces.
Cricket has copy to sql support built into the application now, I thought about using that for this purpose. I elected to have an offline process inserting data into SQL for a couple of reasons: 1) it doesn't require patching MRTG, 2) MRTG is very fast/efficient at polling and writing to its internal data stores (I didn't want to mess with that), 3) I did not want MRTG to be dependant on the SQL server. With the data collection in mrtgsql a second process offline from MRTG you could lower the frequency of the cron job and insert to SQL in bulk once per hour lets say. -Max -- Max Clark Creative Thought, Inc 877.256.8901 Toll Free 310.455.6735 International 310.943.1968 Fax [EMAIL PROTECTED] http://www.cthought.com This transmission may contain privileged and confidential information intended only for the recipient(s) named above. If you have, or believe you have, received this transmission in error, or are not [one of] the intended recipient(s) named above, you must notify the sender immediately and permanently destroy any and all copies of this transmission. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cook, Garry Sent: Tuesday, February 17, 2004 6:53 AM To: Tobias Oetiker Cc: Max Clark; MRTG Mailinglist Subject: [mrtg] Re: mrtgsql - a MRTG to SQL logging and reporting tool Tobias Oetiker wrote: > Today Cook, Garry wrote: >>> Feedback and suggestions are always welcome. >> >> You mentioned .log files... Will this work for .rrd files as well? >> Any plans for such a beast? > > I wondr though, why you would want to write the data into a log or rrd > file first instead of punishing your database server with it right > away ... ? > > tobi Good question. I hadn't really considered that, only had half a cup of coffee this morning... If I had an sql server already setup, I might have thought about it more in depth. I don't know mysql or msql well enough to weigh the pros and cons, although I find rrdtool and .rrd files very clean and easy to manage. It sounds like mrtgsql would add a redundant layer to my setup. However, I've written many scripts that automate the tasks involved with my mrtg installation, it would probably be easier for me to add this extra layer than to rebuild my entire mrtg management system. Perhaps I should have asked, 'Will the second portion of the package, mrtgreport, hook directly to an .rrd?' Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) -- 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