All Apps and Add-ons

JSON MIB translations

Communicator

The SNMP in its default source type of "snmp_ta" isn't very good and the value's in the fields are either too long with unnecessary information or missing key info. The data is very inconsistent.

However, if I use JSON as a source type with the correct response handler the field value pairs create far better data outputs.

However, the MIBs don't appear to be translating the OIDs into their friendly name correctly when I use JSON.

Does anyone know if this is working correctly and if it is possible for the MIB translation to work when we use JSON as the support type?

Tags (1)
0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!