How to set alert resolution states
Important
This version of Operations Manager has reached the end of support. We recommend you to upgrade to Operations Manager 2022.
In System Center Operations Manager there are seven default resolution states for alerts:
Resolution State | ID |
---|---|
New | 0 |
Closed | 255 |
Acknowledge | 249 |
Assigned to Engineering | 248 |
Awaiting Evidence | 247 |
Resolved | 254 |
Scheduled | 250 |
When an alert is generated, its resolution state is New. Operators can change the resolution state for a new alert to Closed or to a custom resolution state that an administrator has created for the management group.
Custom alert resolution states can use any descriptor you want, such as "Assigned to support" or "Requires investigation". The default resolution states can't be changed or deleted.
Each resolution state is assigned an ID, a number which uniquely identifies that resolution state. You can assign custom resolution state that isn't already used, and you can't use a value higher than 255.
To set the resolution state for an alert
In the Operations console, select Monitoring.
Select any view that displays alerts, such as Active Alerts.
Right-click an alert, point to Set Resolution State, and select the desired resolution state.
To create an alert resolution state
In the Operations console, select Administration.
Select Settings.
Double-click Alerts.
On the Alert Resolution States tab, select New.
In Add Alert Resolution State, enter a name for the resolution state, select a value in the Unique ID box, and select OK.
In Global Management Group Settings - Alerts, select OK.
Next steps
Before changing the number of missed heartbeats allowed, first review How Heartbeats Work in Operations Manager.
To learn more about how to investigate an agent heartbeat failure and ways to resolve them, review Resolving Heartbeat Alerts.
When an alert is generated, you can View Active Alerts and Details in the Operations and Web console to identify possible issues and help identify next steps towards resolving them.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for