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 <[EMAIL PROTECTED]> 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."_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
