Splunk Alert MIB - why no OID for severity?

Alerting

I am sure I am reading the MIB correctly. There appears to be no OID for severity.
What methods have sys admins used to work around this?
We are having to get custom handler created in the receiving (external) enterprise management tool. An alternative was to just manually edit the MIB to include severity. Seems the easiest but runs the risk of being overwritten during upgrades.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...