[mrtg] Using symbolic names in Target[] definitions

Freddie Cash fjwcash at gmail.com
Wed May 20 00:56:03 CEST 2009

On Tue, May 19, 2009 at 3:47 PM, McDonald, Dan
<Dan.McDonald at austinenergy.com> wrote:
> On Tue, 2009-05-19 at 15:29 -0700, Freddie Cash wrote:
>> For network interfaces, it's possible to use symbolic names like eth0,
>> em3, lagg0, bond3 and so on in the Target[] definition.  This way, no
>> matter how the devices are enumerated at each boot, the data is polled
>> correctly.  These names are listed in the ifDescr.* variables that
>> have the same index value as the if*Octets.* variables.
>> Is it possible to do the same for any other OIDs that provide *Descr
>> variables?
> For interface variables, which use the same ifNum, certainly.
>> For example, hrStorage* includes hrStorageDescr that links
>> the symbolic names (/, /var, /tmp, and so on) to the specific OID
>> index.
> This capability doesn't currently exist.

Damn, that's what I was afraid of.  :(

Well, since my perl-fu and c-fu are pretty much non-existent.  I'll
see if I can write a wrapper to do this in sh, and wait patiently
until it annoys someone enough to add the support into MRTG.  :)

Freddie Cash
fjwcash at gmail.com

More information about the mrtg mailing list