[mrtg] Log File all 0-values

PAUL WILLIAMSON pwilliamson at mandtbank.com
Wed Mar 21 19:10:16 CET 2007


The rule is that you want to capture the data.  Using the "perminute" 
option will result in the same problem, just less of it.

During regular intervals, if the data increments less than one unit 
per second, the end result is 0.  If it is more than 300 per interval 
(not ironically) of 5 minutes, the value will be some whole number 
greater than 0.

If you have 301 units in a 5 minute window, the value will be one.
If you change it so that the interval is "perminute" (thus not 
perfiveminute), your value will "magically" change from one to five.

301 untis of something in a 5 minute window, as far as network 
traffic goes, is statistically insignificant.  One the other hand, if 
you're graphing something like file transfers and 301 is a big deal, 
either because it doesn't happen that often or you want to know 
the real number, not only should you switch to perminute, you 
should consider multiplying the value by 60 to get the actual data in 
the log file.

Paul

>>> "Brian A. Seklecki" <lavalamp at spiritual-machines.org> 03/21/07 1:58
PM >>>

Yea perminute seemed to be the option argument that fixed things

So what's the rule here? If the couner increments less than 300 ticks
(at 
5 minute intervals), then switch to "perminute" ?

~BAS

On Wed, 21 Mar 2007, Eric Brander wrote:

>> 
>> On 3/20/07, Brian A. Seklecki <lavalamp at spiritual-machines.org>
wrote:
>> >
>> >
>> > It was calling rateup with:
>> >
>> > --log: Called /usr/local/bin/rateup /var/www/htdocs/mrtg/pgsql/
>> > slon.db00.events.mn 1174406129 -Z u 51884 51884 100000000 c
#00cc00
>> > #0000ff #006600 #ff00ff l [events] k 1000 i
>> > /var/www/htdocs/mrtg/pgsql/slon.db00.events.mn-day.png -100000000
>> > -100000000 400 100 1 1 1 300 0 4 1 %Y-%m-%d %H:%M 0
>> >
>> > --log: Called /usr/local/bin/rateup /var/www/htdocs/mrtg/pgsql/
>> > slon.db00.events.mn 1174406108 -Z u 51874 51874 100000000 c
#00cc00
>> > #0000ff #006600 #ff00ff l [events] k 1000 i
>> > /var/www/htdocs/mrtg/pgsql/slon.db00.events.mn-day.png -100000000
>> > -100000000 400 100 1 1 1 300 0 4 1 %Y-%m-%d %H:%M 0
>> >
>> > The value was clearly increasing.
>> 
>> 
>
> If you're doing a rate, then your rate is increasing at < 1 per
interval, by
> default per second. MRTG won't do fractions. Try PerMinute or
PerHour
> options and see if that gets you more useful data.
>
> -- 
> Eric Brander
>

l8*
 	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
 	       http://www.spiritual-machines.org/ 

"...from back in the heady days when "helpdesk" meant nothing,
"diskquota"
meant everything, and lives could be bought and sold for a couple of
pages
of laser printout - and frequently were."



More information about the mrtg mailing list