[mrtg] Re: MRTG: value without division per time interval (no gauge)

[Pete Templin]

Yeah, MRTG works in rates.  But I don't want to know how many BGP updates occurred per second, I want to know how many BGP updates occurred since the last time I checked.  I don't want per minute, I don't want per hour; they don't give a resolution that's extremely useful.  I see 100 to 500 updates every five minutes.  That'd be 20-100 updates per minute, but if the graph is 135 pixels tall, I'd rather not lose 4/5 of my precision.  I don't want to write an external program interface when there's an OID readily available to me.  Is that so hard to understand?

Besides, if you were to draw a matrix of the combinations possible (calculate the difference or read the current value, divide by the interval or not), you'd see that there are four combinations but only three of them can be achieved in current form (native, gauge, absolute).  Is it really so hard for folks to realize that, and maybe consider that there is a valid use for it?  

*putting fresh flame suit on*

Pete Templin
Senior Staff Engineer
TexLink Communications
(210) 892-4183
pete.templin at texlink.com


-----Original Message-----
From: Alex van den Bogaerdt [mailto:alex at ergens.op.het.net]
Sent: Friday, September 12, 2003 8:05 AM
To: MRTG MRTG
Subject: [mrtg] Re: MRTG: value without division per time interval (no gauge)

On Fri, Sep 12, 2003 at 07:56:20AM -0500, Pete Templin wrote:

> What's needed is an option ("events"?) that calculates the difference between the previous poll and the current poll, and simply displays that.  Default calculates the difference and divides by the interval.  Gauge shows the current poll and doesn't divide by the interval.  Absolute shows the current poll divided by the interval.  "Newoption" would calculate the difference but not divide by the interval.

No, this is not needed.  MRTG works in rates.  Numbers per second.
GAUGE is a way to tell MRTG that the number is already a rate.
It is still a rate, per second.

Events per <unknown time> are rates but they are not in the
events per second format.  *If* you write a front end (the external
program interface comes to mind) that translates "events per unknown"
into "other number of events per second" then you can use GAUGE just
fine.

Alex
--
http://www.googlism.com/index.htm?ism=alex+van+den+bogaerdt&type=1

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi