[mrtg] Re: mrtgsql - a MRTG to SQL logging and reporting tool

[Max Clark]

Logging every datasource to mysql will definitely be slower and less
efficient than logging to .rrd. People that are writing to mysql will have
to monitor the size of their database and most likely create a data
warehouse of some kind for "old" data.

I am not advocating the unilateral use of mrtgsql for all of the datasources
in the MRTG config, only the ones where detailed reporting (in my case for
billing) is necessary.

-Max


--
Max Clark
Creative Thought, Inc
877.256.8901 Toll Free
310.455.6735 International
310.943.1968 Fax
max at cthought.com

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: mrtg-bounce at list.ee.ethz.ch [mailto:mrtg-bounce at list.ee.ethz.ch] On
Behalf Of Tobias Oetiker
Sent: Tuesday, February 17, 2004 7:29 AM
To: Marc Bilodeau
Cc: 'MRTG Mailinglist'
Subject: [mrtg] Re: mrtgsql - a MRTG to SQL logging and reporting tool

Today Marc Bilodeau wrote:

> Good question tobi, at Somix our denika/webnm products write the 
> polled data to both the RRD files and the MySQL back-end. We believe 
> that users should have a quick reference for daily, weekly, monthly, 
> and yearly data. However, if the user needs to create a report based 
> on 5 minute samples between 8am and 5pm for Tuesday, Thursday, and 
> Friday on the week of October 23 they can with the stored data. Some 
> would argue by increasing the amount of data that can be stored in the 
> rrd file would do the trick. However, many other tools out there can 
> take advantage of the database via ODBC or a direct connection.

Hi Marc,

Yep, that seems like a sensible thing .... I would assume though that in a
setup with MANY datasources, that mysql may probably not be able to keep up
or fill up quickly if no data is deleted ...

have you done any tests in this direction ? mysql vs rrd performance?

cheers
tobi


-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker @ ISG.EE, ETZ J97, ETH, CH-8092 Zurich  / // _ \/
_ \/ /  System Manager, Time Lord, Coder, Designer, Coach
/_/ \.__/_.__/_/   http://people.ee.ethz.ch/~oetiker   +41(0)1-632-5286

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
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:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
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