On 07/06/06 Alex van den Bogaerdt said: > Four counters, nothing special. Three observations: > 1) the order of these DSes is not the same as you describe above. > 2) the input needs to be increasing numbers, like odometers. > 3) you use LAST, I wonder why
1. my fault for not typing them in the same order, but they are everywhere else 2. the numbers are constantly increasing 3. I use LAST because I don't want to average the numbers. Perhaps I misunderstand LAST. Could you offer an explanation? I thought that it was just the last data point. > Modify your perl wrapper so that it does two things: > 1) generate a timestamp > 2) write this timestamp and the rrdtool update command to a txt logfile > > This is best done like this: > > "rrdtool update mailqueue.rrd 1149671400:4155:1976:2316:134" > (without the quotes) > > This makes it possible to analize your input and to reply the > process without much effort. Sure. > > Then, I make a graph, plotting the four lines against time. > > > > /usr/local/bin/rrdtool graph mailqueue_daily.png -a PNG \ > > --title="Postfix Mailqueue (24 hrs)" \ > > --vertical-label="Email rate (email/hr)" \ > > You have "per second", you want "per hour" so you need to multiply > by 3600. I thought that with COUNTERs, the rate was per interval, not per second. > > > --start $one_day_ago --end $now \ > > could be: --start end-24h --end $now > or similar Ok, cool. Could --end be N? > > 'DEF:myincoming=mailqueue.rrd:incoming:AVERAGE' \ > > 'DEF:myreceived=mailqueue.rrd:received:AVERAGE' \ > > 'DEF:myrejected=mailqueue.rrd:rejected:AVERAGE' \ > > 'DEF:mysent=mailqueue.rrd:sent:AVERAGE' \ > > 'CDEF:incoming_perhour=myincoming,12,*' \ > > 'CDEF:received_perhour=myreceived,12,*' \ > > 'CDEF:rejected_perhour=myrejected,12,*' \ > > 'CDEF:sent_perhour=mysent,12,*' \ > > These multiplications result in "per 12 seconds". ah. Might explain why two lines aren't showing up, as they're just not increasing fast enough. > try using \n for a new line. Ok, I'll try that. > RRDtool works with rates. See my site for an explanation. It comes down to: > what ever you have in the front; the result is always "something per second". OK... > The other two lines could be hidden on the X-axis. Unlikely, but possible. > Try plotting one line at a time (during debugging of course). > > Use the debug output I suggested and do some calculations by hand. They > should match what RRDtool is producing. > > Make sure your input is like an odometer. If it's not, you have to change > your data source type (or your input). Thanks, I'll try this and report back. Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein -- Binary/unsupported file stripped by Ecartis -- -- Err : No filename to use for decode, file stripped. -- Type: application/pgp-signature -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
