It looks like this is related to the resolution interval of the graph function.
Of course the graphs put out the right peak for 24hour graphs - there are only 288 data points to contend with, which easily fits into the 400px graph. The problem starts when I have more data points than pixels. RRDGraph seems to be doing some consolidation on those data points to make them fit (makes sense). My (new) question is this: if these RRAs are set up to use MAXIMUM and I am calling VDEFs with MAXIMUM, why are the graphs returning different numbers? Shouldn't the longer time frames simply have consolidated the data by taking the max data points and tossing the rest? More importantly, why is RRDGraph returning values that are *higher* than the actual max that RRDFetch returns? Hope someone can help - I'm really starting to get confused. -- View this message in context: http://n2.nabble.com/RRDTool-Aggregation-Inaccuracies.-tp3217529p3228853.html Sent from the RRDtool Users Mailinglist mailing list archive at Nabble.com. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
