"Sheahan, John (PCLN-NW)" wrote: > > HAHA! > > Thanks for giving me a little laughter this morning Alex! > I will follow your direction but it might take a couple of weeks to sort > through it all. I will however, follow up and get back to you with my > results. Thanks for the help!
Oh but I really think it shouldn't be too hard to do. As long as you keep your database in a format suitable for rrdtool it probably is going to be (relatively) easy. If not, you will have to do normalizing and in that case it is better to just input the data as you would normally do. For starters: - if you only have one database, it is always going to be the best match - rrdtool asks for <start> to <end>, at resolution <r>. You will have to return data and tell rrdtool what the real values became - don't forget that an interval in rrdtool is defined by its *end*time To me it looks as easy as implementing a new rrd_fetch_fn() that uses a database lookup from SQL. There will (of course) be some problems to solve but that's half the fun! cheers, -- __________________________________________________________________ / [EMAIL PROTECTED] [EMAIL PROTECTED] \ | work private | | My employer is capable of speaking therefore I speak only for myself | +----------------------------------------------------------------------+ | Technical questions sent directly to me will be nuked. Use the list. | +----------------------------------------------------------------------+ | http://faq.mrtg.org/ | | http://rrdtool.eu.org --> tutorial | +----------------------------------------------------------------------+ -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-developers WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
