What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

We need to assign an appropriate severity or criticality to each Ops Manager alert configuration. Currently, we do not see an option to set it when creating or editing an alert. Severity is determined by Ops Manager’s event type rather than the operational importance of that alert to us. As a result, alerts cannot carry our intended priority when they trigger.

What would you like to see happen?

Describe the desired outcome or enhancement.

Allow us to choose or override severity for each Ops Manager alert configuration in the UI and API, with a documented default if we leave it unset. Show the effective severity on the configuration and generated alert, so we can use it consistently for prioritization and integrations.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Our response urgency depends on the impact of a particular alert in our environment. Configurable severity would help our operations team distinguish high-impact alerts from lower-priority ones, route incidents appropriately, and avoid relying on an event type alone to represent business criticality.

What steps, if any, are you taking today to manage this problem?

Today we configure alert conditions and notification methods in Ops Manager, but cannot set severity per alert configuration. Where different priorities are needed, they have to be assigned outside Ops Manager—for example, through a mapping based on the alert’s event type in the receiving system.