[rrd-users] Questions about effective database parameters

[Henrik Hegardt]

Hello.
I'm writing a program to monitor a server's activities. Its about response times for services on the server. There are quite many services and most of the written data are unknowns. The response times is quite crucial and would want to have as high resolution as possible even though there are unknowns. If there's a response time I write it to the DB with 1 second interval though since there are several other services per rrd a update operation could look like 'update database.rrd 1292313983:U:U:U:U:U:U:U:0.012:U:U:U:U:U:U'. I would like to store it for atleast 6 months and thus view it over that time. I'm not interested of if there was no value, but the value itself.
I can't tell if there will be a lot of updates during a time interval or none at all which should result in some of the entries won't even get a 'U' value (most probably).
I have worked with following
rrdtool create -s 1 \
DS:ds1:GAUGE:2:0:3600 \
...
RRA:AVERAGE:0.5:30:720 
RRA:AVERAGE:0.5:60:720 
RRA:AVERAGE:0.5:420:720
RRA:AVERAGE:0.5:1800:720 
RRA:MAX:0.5:30:720 
RRA:MAX:0.5:60:720 
RRA:MAX:0.5:420:720 
RRA:MAX:0.5:1800:720

This didn't work, since I believe there a lot more 'U' values than 0.5 and the resolution isn't good enough and really doesn't make sense according to what I'm trying to sample.
RRA:AVERAGE:0.5:1:86400 worked but then having a rra over 6 months (6*30*86400) will result in a big db and slow rendering of images. Any ideas?

Forgive my English.


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/rrd-users/attachments/20101214/1a69ca78/attachment.htm