Want this feature implemented, too? Please upvote by clicking Thumbs up!
(Posts as a reply won't be published in this feature request thread. Read Me!)
User story
As a PRTG user, I want multicolumnar SNMP table support without resorting to manual custom SNMP table sensor creation.
Details of user story
We use F5 (https://kb.paessler.com/en/topic/78889-custom-snmp-table-with-multiple-indexes) and Raritan (http://cdn.raritan.com/download/PXE/v3.2.10/mib-usage.pdf - pg. 12 sec. 5.3) devices that PRTG cannot monitor very easily.
Many of the interesting OIDs are tables with multiple rows and columns. The MIBs supplied by the vendor use multiple indexes to extract data from these tables. The Paessler MIB Importer does not support multiple indexes (MIB Importer Manual - pg. 41) and ignores most of the useful objects.
We need to monitor outlet current, voltage, etc. on a Raritan Power Distribution Unit (PDU) at our data centers.
Some of our other monitoring platforms import MIB table objects with multiple indexes. Why can't PRTG?
Acceptance criteria
- Criterion #1 - understand and import objects from MIBs using multiple indexes
- Criterion #2 - allow easy library or table sensor creation without manually walking/identifying/configuring custom sensors for each new device model/type This basically gives us a set of cornerstones that need to be there in order for the feature to be implemented.
Status
Open
Last change on Feb 18, 2021 10:41:08 AM by
