The All Alerts page is a list of all the alerts generated in vRealize Operations Manager. Use the alert list to determine the state of your environment and to begin resolving problems.

How the All Alerts Page Works

By default, only active alerts are initially listed, and the alerts are grouped by Time. Review and manage the alerts in the list using the toolbar options. Select multiple rows in the list using Shift+click, Control+click.

To filter the columns in the data grid, click the small box on the lower left of the alert list.

To see the alert details, click the alert name. The alert details appear on the right, including the symptoms triggered by the alert. The system offers recommendations for addressing the alert and links to additional information. A Run Action button may appear in the details. Hover over the button to learn what recommendation is performed if you click the button. Click the X at the top right of the alert details to return to the list view.

Click the name of the object on which the alert was generated to see the object details, and access additional information relating to metrics and events.

If you migrated alerts from a previous version of vRealize Operations Manager, the alerts are listed with a cancelled status and alert details are not available.

Where You Find the All Alerts Page

In the menu, click Alerts.

All Alerts Options

The alert options include toolbar and data grid options. Use the toolbar options to sort the alert list and to cancel, suspend, or manage ownership. Use the data grid to view the alerts and alert details.

Select an alert from the list to enable the Actions menu:

Table 1. Actions Menu



Cancel Alert

Cancels the selected alerts. If you configure the alert list to display only active alerts, the canceled alert is removed from the list.

Cancel alerts when you do not need to address them. Canceling an alert does not cancel the underlying condition that generated it. Canceling alerts is effective if the alert is triggered by fault and event symptoms, because these symptoms are triggered again only if subsequent faults or events occur on the monitored objects. If the alert was generated based on metric or property symptoms, the alert is canceled only until the next collection and analysis cycle. If the violating values are still present, the alert is generated again.


Suspend an alert for a specified number of minutes.

You suspend alerts when you are investigating an alert and do not want the alert to affect the health, risk, or efficiency of the object while you are working. If the problem persists after the elapsed time, the alert is reactivated and it will again affect the health, risk, or efficiency of the object.

The user who suspends the alert becomes the assigned owner.

Take Ownership

As the current user, you make yourself the owner of the alert.

You can only take ownership of an alert, you cannot assign ownership.

Release Ownership

Alert is released from all ownership.

Go to Alert Definition

Switches to the Alert Definitions page, with the definition for the previously selected alert displayed.


Offers two options for disabling the alert:

Disable the alert in all policies: this disables the alert for all objects for all the policies.

Disable Alert in Selected Policies: this disables the alert for objects having the selected policy. Note that this method works only for objects with alerts.

Open an external application

Actions you can run on the selected object.

For example, Open Virtual Machine in vSphere Client.

Table 2. Group By Options




Alerts are not sorted into specific groupings.


Group alerts by time triggered. The default.


Group alerts by criticality. Values are, from the least critical: Info/Warning/Immediate/Critical. See also Criticality in the "All Alerts Data Grid Options" table, below.


Group alerts by definition, that is, group like alerts together.

Object Type

Group alerts by the type of object that triggered the alert. For example, group alerts on hosts together.

Table 3. All Filters

All Filters


Filtering options

Limit the list of alerts to those matching the filters you choose.

For example, you might have chosen the Time option in the Group By menu. Now you can choose Status -> Active in the all Filters menu, and the All Alerts page displays only the active alerts, ordered by the time they were triggered.

Selected Options (see also the Group By and All Alerts Data Grid tables for more filter definitions:)


Name of operator who owns the alert.


Alert badge affected by the alert. The affected badge, health, risk, or efficiency, indicates the level of urgency for the identified problem.

Control State

State of user interaction with the alert. Possible values include:

  • Open. The alert is available for action and has not been assigned to a user.

  • Assigned. The alert is assigned to the user who is logged in when that user clicks Take Ownership.

  • Suspended. The alert was suspended for a specified amount of time. The alert is temporarily excluded from affecting the health, risk, and efficiency of the object. This state is useful when a system administrator is working on a problem and does not want the alert to affect the health status of the object.

Object Type

Type of object on which the alert was generated.

Updated On

Date and time when the alert was last modified.

An alert is updated whenever one of the following changes occurs:

  • Another symptom in the alert definition is triggered.

  • Triggering symptom that contributed to the alert is canceled.

Canceled On

Date and time when the alert canceled for one of the following reasons:

  • Symptoms that triggered the alert are no longer active. Alert is canceled by the system.

  • Symptoms that triggered the alert are canceled because the corresponding symptom definitions are disabled in the policy that is applied to the object.

  • Symptoms that triggered the alert are canceled because the corresponding symptom definitions were deleted.

  • Alert definition for this alert is disabled in the policy that is applied to the object.

  • Alert definition is deleted.

  • User canceled the alert.

The Alerts data grid provides the list of generated alerts used to resolve problems in your environment. An arrow in each column heading orders the list in ascending or descending order.

Table 4. All Alerts Data Grid




Criticality is the level of importance of the alert in your environment.

The level is based on the level assigned when the alert definition was created, or on the highest symptom criticality, if the assigned level was Symptom Based.

The possible values include:

  • Critical

  • Immediate

  • Warning

  • Information


Name of the alert definition that generated the alert.

Click the alert name to display the alert details to the right.

Triggered On

Name of the object for which the alert was generated, and the object type, which appears in a tooltip when you hover the mouse over the object name.

Click the object name to view the object details tabs where you can begin to investigate any additional problems with the object.

Created On

Date and time when the alert was generated.


Current state of the alert.

Possible values include Active or Canceled.

Alert Type

Describes the type of alert that triggered on the selected object, and helps you categorize the alerts so that you can assign certain types of alerts to specific system administrators. For example, Application, Virtualization/Hypervisor, Hardware, Storage, and Network.

Alert Subtype

Describes additional information about the type of alert that triggered on the selected object, and helps you categorize the alerts to a more detailed level than Alert Type, so that you can assign certain types of alerts to specific system administrators. For example, Availability, Performance, Capacity, Compliance, and Configuration.