Cheshire Cat Computing

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.

Is it possible to do the same for any other IODs that provide *Descr variables? For example, hrStorage* includes hrStorageDescr that links the symbolic names to the specific IOD index. Is there anyway to use this symbolic name (as shown in the *Descr output) instead of the OID numbers?

It's really annoying to have to double-check everything in the config file after a server is rebooted, and to manually update the Target[] lines to match how things got enumerated this time.

Currently, this is not possible, but it would be really good to have this as an extension to the Target syntax, if there were some convenient way to define it. It would be a natural generalisation of the way interface identification is done, and very useful for disk and filesystem monitoring. Maybe some syntax like -

TaBLEtableoid(suboid=value).othersub

would work? Its a bit messy, though, and not in line with the other formats. Might be easier if we assume all tables correctly use an Index subOID on .1 and the matching OID is on .2?

This should really go to the MRTG-developers list or to Tobi as a wishlist item...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11