[rrd-users] Cricket/RRD fetch resolution problem (2nd try)
Scott C. Kennedy
sck at s4r.com
Thu Aug 2 21:22:19 MEST 2001
I am running RRDTool 1.0.33 within Cricket-1.0.2 and have a problem with the
resolution of data that I pull out via RRD:fetch (either through the Perl
Module or through the command line rrdtool).
The issue is that I have my RRDs set up like this (via the cricket config
file)
# one point per 5 minutes, spanning 50 hours
rra 5minAve AVERAGE:0.5:1:600
# one point per 5 minutes, spanning 366 days
rra 5minUse AVERAGE:0.5:1:105500
# one point per 30 minutes, spanning 12 days
rra 30minAve AVERAGE:0.5:6:600
# one point every 2 hours, spanning 50 days
rra 2hrAve AVERAGE:0.5:24:600
# one point every day, spanning 600 days
rra 1dayAve AVERAGE:0.5:288:600
# we will add datasources to each specific target-type later
targetType --default--
rra = "5minAve, 30minAve, 2hrAve, 1dayAve,
5minUse"
And when I do a query for "-s "now-1month" I should pull 8930 values from the
"5minUse" RRA, but sometimes I pull 374 values which seem to come from the
"2hrAve" RRA instead of the "5minUse" RRA. Now, I have some RRDs no longer
being updated, due to the switch not being used anymore, and the data is
historical, but still valid, and the problem doesn't seem to be related to the
last updated field.
Here's a short example.
# ls -la data1.rrd
-rw-r--r-- 1 usage 5000 1728368 Jul 23 11:00 data1.rrd
# ls -la data2.rrd
-rw-r--r-- 1 usage 5000 1728368 Aug 1 19:40 data2.rrd
# rrdtool fetch data1.rrd AVERAGE -s now-1month > /tmp/ck1
# rrdtool fetch data2.rrd AVERAGE -s now-1month > /tmp/ck2
# ls -la /tmp/ck*
-rw-r--r-- 1 sck 10000 14307 Aug 1 19:35 /tmp/ck1
-rw-r--r-- 1 sck 10000 357131 Aug 1 19:35 /tmp/ck2
# rrdtool info data1.rrd
filename = "data1.rrd"
rrd_version = "0001"
step = 300
last_update = 995911215
ds[ds0].type = "COUNTER"
ds[ds0].minimal_heartbeat = 1800
ds[ds0].min = NaN
ds[ds0].max = NaN
ds[ds0].last_ds = "3731434832"
ds[ds0].value = 2.5620270000e+05
ds[ds0].unknown_sec = 0
ds[ds1].type = "COUNTER"
ds[ds1].minimal_heartbeat = 1800
ds[ds1].min = NaN
ds[ds1].max = NaN
ds[ds1].last_ds = "4093198491"
ds[ds1].value = 1.6657900000e+04
ds[ds1].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 600
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[0].cdp_prep[1].value = NaN
rra[0].cdp_prep[1].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 600
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = NaN
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[1].value = NaN
rra[1].cdp_prep[1].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 600
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = NaN
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[2].cdp_prep[1].value = NaN
rra[2].cdp_prep[1].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 600
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 2.5397145070e+06
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[3].cdp_prep[1].value = 2.4025527222e+05
rra[3].cdp_prep[1].unknown_datapoints = 0
rra[4].cf = "AVERAGE"
rra[4].rows = 105500
rra[4].pdp_per_row = 1
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[4].cdp_prep[1].value = NaN
rra[4].cdp_prep[1].unknown_datapoints = 0
# rrdtool info data2.rrd
filename = "data2.rrd"
rrd_version = "0001"
step = 300
last_update = 996719709
ds[ds0].type = "COUNTER"
ds[ds0].minimal_heartbeat = 1800
ds[ds0].min = NaN
ds[ds0].max = NaN
ds[ds0].last_ds = "2422928211"
ds[ds0].value = 6.6776363636e+03
ds[ds0].unknown_sec = 0
ds[ds1].type = "COUNTER"
ds[ds1].minimal_heartbeat = 1800
ds[ds1].min = NaN
ds[ds1].max = NaN
ds[ds1].last_ds = "482603768"
ds[ds1].value = 1.4450606061e+03
ds[ds1].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 600
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[0].cdp_prep[1].value = NaN
rra[0].cdp_prep[1].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 600
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = 8.4367180815e+02
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[1].value = 1.7898019533e+02
rra[1].cdp_prep[1].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 600
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = 8.2131523232e+03
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[2].cdp_prep[1].value = 1.6087467980e+03
rra[2].cdp_prep[1].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 600
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 7.0464442498e+04
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[3].cdp_prep[1].value = 1.0056682913e+04
rra[3].cdp_prep[1].unknown_datapoints = 0
rra[4].cf = "AVERAGE"
rra[4].rows = 105500
rra[4].pdp_per_row = 1
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[4].cdp_prep[1].value = NaN
rra[4].cdp_prep[1].unknown_datapoints = 0
So, is this a resolution problem? Is RRD looking at the last update and
deciding that this data is too old, or what?
Scott
--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
More information about the rrd-users
mailing list