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

You cancel alerts when you do not need to address them. Canceling the alert does not cancel the underlying condition that generated the alert. Canceling alerts is effective if the alert is generated by triggered fault and event symptoms because these symptoms are triggered again only when subsequent faults or events occur on the monitored objects. If the alert is 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.

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

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

Alert is released from all ownership.

Deactivate the alert in all policies: this deactivates the alert for all objects for all the policies.

Deactivate Alert in Selected Policies: this deactivates the alert for objects having the selected policy. This method works only for objects with alerts.

For example, Open Virtual Machine in vSphere Client.

Displays the alerts for the ancestors of the selected object.

Parents in this instance include the parents, grandparents, and so on, of the object. For example, the parents of a host are a folder, storage pod, cluster, data center, and instance.

Displays the alerts for the descendants of the selected object.

Children in this instance include the children and grandchildren of the object. For example, the descendants of a host are datastores, resources pools, and virtual machines.

The advanced search and filter lets you search for a symptom by:

Alert ID
Alert
Owner
Impact
Alert Type
Alert Subtype
Status
Criticality
Triggered On
Control State
Object Type
Created On
Updated On
Canceled On
Action

Criticality is the level of importance of the alert in your environment. The alert criticality appears in a tooltip when you hover the mouse over the criticality icon.

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 view the alert details tabs where you can begin troubleshooting the alert.

Date and time when the alert was generated.

Current state of the alert.

Possible values include Active or Canceled.

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, Network, Administrative, and Findings.

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.