[mrtg] With "options[target]: gauge" MRTG updates the RRD file with one value, but fetch returns a different (averaged) value

Volk,Gregory B greg.volk at edwardjones.com
Fri Apr 20 14:38:03 CEST 2007

>If you see 1 user connected at 9:56am, 5 users connected at 
>10:01am and 7 users connected at 10:06am, what would you 
>rrdtool want to store for the periode 10:00am to 10:05am

Yes, that makes sense now that I think about it further. I suppose I was
looking to load one number without modifications for each 300 second
interval, and when requested, rrdtool would return back the original
value for any request that fell into the 300 second interval. So if the
data was...

09:56		1

10:01		5

10:06		7

...and I asked for the record for 10:00 it would return 1 (the value it
had for that 300 second interval), and for 10:04 it would return 5, and
for anywhere from 10:06:00 to 10:11:00 it would return 7. I see why it
doesn't work like this now. Thanks for the explanation. I was under the
mistaken impression that GAUGE data was stored unmodified in the RRD
other than the averages calculated and stored in the RRAs.

More information about the mrtg mailing list