All Apps and Add-ons

JSON MIB translations

arrowecssupport
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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...