[mrtg] Config file help
scheesman at caeveo.com
Tue Jan 20 05:21:11 CET 2009
Try gauge then.
Treat the values gathered from target as 'current status' measurements and not as ever incrementing counters. This would be useful to monitor things like disk space, processor load, temperature, and the like ...
In the absence of 'gauge' or 'absolute' options, MRTG treats variables as a counters and calculates the difference between the current and the previous value and divides that by the elapsed time between the last two readings to get the value to be plotted.
From: mrtg-bounces at lists.oetiker.ch [mrtg-bounces at lists.oetiker.ch] On Behalf Of John [john at thetethered.com]
Sent: Monday, January 19, 2009 11:15 PM
To: Steve Shipway
Cc: 'mrtg at lists.oetiker.ch'
Subject: Re: [mrtg] Config file help
Steve Shipway wrote:
> What do these values represent?
> So, is this a count of the total time spent on battery (ever)? You want to
> see a graph with a constantly increasing line? In this case, you need to
> add the option 'gauge'.
> In the absence of the 'gauge' option, MRTG will graph the rate of change of
> this value (this is the default behaviour as this is what you'd need if the
> counter were a count of total network traffic and you wanted a bandwidth
> utilisation graph). Hence you get zeros as the value does not change.
The first output is total time on battery from last restart, not total
time remaining. The second output is always 0, the script outputs a 0
just in case the "noo" option was missed. The third output will be the
current up time when I get it fixed. The forth output is the device name.
I don't think I want the gauge option, I want to count how many seconds
on battery from the last power failure, not from last restart.
Hopefully they're not the same.
I have tried the absolute option but that got me to same place, all
zeros in my log file.
More information about the mrtg