You can create custom metric classes that populate metrics by reading data from multiple MIB tables as NetIM can perform table merge by using various mechanisms.

Converters can be used to manipulate the collected MIB data and customize the generated metric data. With converters, there is more control over the metric data generated for custom metric classes and it is possible to override how metric data is generated for out-of-the-box metric classes. For example, Default Value converter returns the object identifier (OID) value from the given MIB table. Delta Value converter returns the delta value between the current polled value and the previous polled value for the given MIB table and OID. Raw Value converter returns the current polled value for the given MIB table and OID even if it is a Counter type OID.

You can easily add support for an out-of-the-box metric class for an existing vendor with a new device type (with a new system object ID) or a new vendor (with an unsupported system object ID). If an existing MIB table is not supported for the new device type or the new vendor, a new MIB table can be selected, and converters can be used to populate the metrics. Similarly, for an already supported vendor, the behavior can be overridden by using the existing MIB table and configuring converters or by using a new MIB table and configuring converters to handle this new MIB table.

You can remove any of the customizations made earlier and restore the out-of-the-box behavior.