Helpful reference for Ops Mgr Priorities and Severities
Found this the other day while I was looking for something to confirm what I thought where the relationships between the numerical values in alerts and the text labels you have to choose from configuring subscriptions (and overrides).
Alert Severity
- Critical = 2
- Warning = 1
- Information = 0
Alert Priority
- High = 2
- Medium = 1
- Low = 0
As an example of how I’m using this knowledge for a specific problem…I only want alerts from the AD Client Connectivity Monitor to come to me as I’m troubleshooting some time-out issues, etc. I have a subscription that send all Critical alerts out to our whole group of admins, and another subscription that sends me the Warning alerts separately. The net effect is that I get both Warning and Critical, but no one else in my group has to deal with the noisy AD Client Connectivity Monitor while I’m working on the issue at hand. Once that issue has been resolved, I’ll remove the override from the monitor, setting its Alert Severity back to its default value of Critical.
What the alert looked like before the override:
Source: AD Client Monitoring
Path: myserver.local
Alert: AD Client Monitoring: AD Connectivity is unavailable, or the response is too slow Resolution state: Closed
Priority: 1
Severity: 2
What the alert looked like after the override:
Source: AD Client Monitoring
Path: myserver.local
Alert: AD Client Monitoring: AD Connectivity is unavailable, or the response is too slow Resolution state: Closed
Priority: 1
Severity: 1
Of course, the value of knowing the numerical relationship of each severity and priority goes beyond just making overrides easier to configure if you have a noisy or otherwise troublesome monitor or rule. Many organizations use the various severity levels as filters when configuring different subscriptions. If you’re developing your own monitors, you’ll need to have a clear understanding of these values of well.
-
Translator
