[mrtg] Fwd: Target did not eval into defined data problem
dan.mcdonald at austinenergy.com
Mon Jun 18 15:23:29 CEST 2012
On 6/18/12 7:49 AM, "Attila Rajmund Nohl" <attila.r.nohl at gmail.com> wrote:
> This is an absolute measure. It's memory usage of a process and is
> only updated every 15 minutes.
That's not the meaning of absolute, it is most likely a gauge.
Absolute resets the counter to zero after polling. It is displayed as a
rate after dividing by 300 (or whatever the polling interval is). There is
no counter rollover taken into account.
Counter assumes a continuously monotonically increasing value with
roll-overs. It is expressed as a rate.
Gauge is a snapshot of data that should be displayed as is and not
considered as a rate.
Daniel J McDonald, CCIE # 2495, CISSP # 78281
> 2012/6/9 Steve Shipway <s.shipway at auckland.ac.nz>:
>> Possibly you should be using the 'gauge' option? Is this variable a counter,
>> or an absolute measure?
>> Also the rate of change may be < 1 per sec. If this is the case, native mode
>> MRTG cannot cope with it, you need RRDTool as your backend.
>> Steve Shipway
>> University of Auckland ITS
>> UNIX Systems Design Lead
>> s.shipway at auckland.ac.nz
>> Ph: +64 9 373 7599 ext 86487
>> Now I don't get errors, but the data is not updated either. This is
>> how the first few lines of the <target>.log file look like:
>> 1339164901 340201472 340201472
>> 1339164901 0 0 0 0
>> 1339164611 0 0 0 0
>> 1339164600 0 0 0 0
>> 1339164300 0 0 0 0
>> mrtg at lists.oetiker.ch
> mrtg mailing list
> mrtg at lists.oetiker.ch
More information about the mrtg