[mrtg] Re: Disk Utilization

[Martinez, Samson]

The graph doesn't seem to respond to the "kMG" entry. Below you will find
the section of the config referencing the disk utilization graph. If I leave
the field empty, the legend below the graph removes all multiplier prefixes
but the "k" stays on the Y axis. If I enter the section like below, all I
get is the "k" prefix. Does the fact that I'm using 14all.cgi and RRDTool
have anything to do with this anomaly? Or, probably more like it, is it
something I'm not doing properly in the config?

Again, many thanks for all assistance.

YLegend[lsausc03.storageUsed]: Disk Free (MB)
Options[lsausc03.storageUsed]: growright, gauge, absolute
Unscaled[lsausc03.storageUsed]: dwmy
Target[lsausc03.storageUsed]:
.1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58&.1.3.6.1.4.1.311.1.1.3.
1.1.5.1.4.6.48.58.48.58.67.58:public at 10.1.2.5
kilo[lsausc03.storageUsed]: 1024
MaxBytes[lsausc03.storageUsed]: 2999
Title[lsausc03.storageUsed]: Disk Space Available
ShortLegend[lsausc03.storageUsed]: B
kMG[lsausc03.storageUsed]: M,G,T,P,E
Legend1[lsausc03.storageUsed]: Space Available on C:
Legend2[lsausc03.storageUsed]: Space Available on C:
LegendI[lsausc03.storageUsed]: C:
LegendO[lsausc03.storageUsed]: C:
PageTop[lsausc03.storageUsed]: <H1>Space Available (One megabyte = 1,048,576
bytes)

Regards,

Samson  


-----Original Message-----
From: Alex van den Bogaerdt [mailto:alex at slot.hollandcasino.nl]
Sent: Friday, February 16, 2001 5:35 PM
To: Martinez, Samson
Cc: mrtg at list.ee.ethz.ch
Subject: Re: [mrtg] Disk Utilization

Martinez, Samson wrote:

> The disk is a 2Gig drive and the space available is 1.6Gig. However, the
> graph always throws a k in front of the space available. For example, it
> says I have 1.6 kMb available. How can I fix that? Many thanks for all
> assistance.

The OIDs you described obviously return space in semi-megabytes.
First thing to do is to let MRTG know you don't want the real thing
but rather the 1024 bytes per kilo variant.  If memory serves well,
this is "Kilo[target]: 1024" (but do check this in the docs).

Then, you need to tweak MRTG so that it knows about the "M".
Normally, MRTG works with bytes, not megabytes. Either multiple
the incoming value by 1024*1024 or alter the kMG values to
display alternative prefixes (so your "kMB" would become "GB").
In essence this tells MRTG that you already have "mega"s and if
you do it right, all prefixes will be okay.  Again if memory
serves well:
"kMG[Target]: M,G,T,P,E" together with "ShortLegend[Target]: B"
This would display "MB" where MRTG would normally display "B",
"GB" where normally "kB" and so on.

cheers,
--
   __________________________________________________________________
 / alex at slot.hollandcasino.nl                  alex at ergens.op.het.net \
| work                                                         private |
| My employer is capable of speaking therefore I speak only for myself |
+----------------------------------------------------------------------+
| Technical questions sent directly to me will be nuked. Use the list. |
+----------------------------------------------------------------------+
| http://faq.mrtg.org/                                                 |
| http://rrdtool.eu.org  --> tutorial                                  |
+----------------------------------------------------------------------+

--
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