If MRTG must convert into PER SECOND, why is it so hard to convert into PER
INTERVAL? There are options to show per minute (but out of the box it can't
poll per minute*), there are options to show per hour, there are options to not
divide by the interval, but there is no option to convert into per interval. I
strongly disagree that I'm using the wrong tool - the graphs that I have
created provide an understandable graphic representation of what I'm trying to
monitor. They're in the same format as a lot of other variables that I
monitor, so boss-types and co-workers can understand and interpret the data
just like lots of other graphs. No one complains about the format. But I had
to use a hack to get the numbers to a readable level ("* 300"), which breaks if
I ever change the interval. The perminute and perhour options automatically
correct for changes in interval, but "* 300" doesn't. There are options that
work great for hourly data, but no option that's a good fit for the default
polling interval.
* Disclaimer: I remember this from the past, but have not verified its accuracy
with present versions. If nothing else, the daily graph doesn't appear to have
room to display a one-minute resolution.
Pete Templin
Senior Staff Engineer
TexLink Communications
(210) 892-4183
[EMAIL PROTECTED]
-----Original Message-----
From: Alex van den Bogaerdt [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 10:02 AM
To: MRTG MRTG
Subject: [mrtg] Re: MRTG: value without division per time interval (no gauge)
On Fri, Sep 12, 2003 at 08:23:53AM -0500, Pete Templin wrote:
> 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?
I think I know MRTG pretty well. What you want to do is not what
MRTG is designed for. Period.
Whatever type of input (counter, absolute, derive, gauge) you are
using doesn't matter: mrtg MUST convert it into <whatever> PER SECOND.
I don't give a shit if there is a valid use for what you are trying
to do; is it really so hard to understand that YOU ARE USING THE
WRONG TOOL.
Collect the numbers, put them in a database and query that database,
sorted on the time stamp, for the last two rows. Simple, no?
You are complaining to the hardware store that you cannot use your
hammer to drive those small screws. And yes, it may be valid to
use small screws. No, do not use a hammer.
Alex
--
Unsubscribe mailto:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
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
