Alerts in vRealize Operations Manager notify you when objects in your environment have a problem. This scenario illustrates one way that you can monitor and process alerts for the objects for which you are responsible.

About this task

An alert is generated when one or more of the alert symptoms are triggered. Depending on how the alert is configured, the alert is generated when one symptom is triggered or when all of the symptoms are triggered.

As the alerts are generated, you must process the alerts based on the negative affect they have on objects in your environment. To do this, you start with Health alerts, and process them based on criticality.

As a virtual infrastructure administrator, you review the alerts at least twice a day. As part of your evaluation process in this scenario, you encounter the following alerts:

  • Virtual machine has unexpected high CPU workload

  • Host has memory contention that a few virtual machines cause

  • Cluster has many virtual machines that have memory contention because of memory compression, ballooning, or swapping

Procedure

  1. In the left pane of vRealize Operations Manager, click the Alerts icon.
  2. In the left pane, click the Health alert lists.

    Health alerts are alerts that require immediate attention.

  3. Place your cursor in the Criticality column, click the down arrow, and select Sort Descending.

    The list is now in order of criticality, with the Critical alerts at the top of the list, followed by Immediate, Warning, and Info alerts.

  4. Review the alerts by name, the object on which it was triggered, the object type, and the time at which the alert was generated.

    For example, do you recognize any of the objects as objects that you are responsible for managing? Do you know that the fix that you will implement in the next hour will fix any of the alerts that are affecting the Health status of the object? Do you know that some of your alerts cannot be resolved at this time because of resource constraints?

  5. To indicate to other administrators or engineers that you are taking ownership of the Virtual machine has unexpected high CPU workload alerts, hold the Ctrl key, click the selected alerts, and click Take Ownership.

    The Owner column updates with your user name. You can only take ownership of alerts, you cannot assign them to other users.

  6. To take ownership and temporarily exclude the alert from affecting the state of the object, select the Host has memory contention caused by a few virtual machines alert in the list and click Suspend.
    1. Enter 60 to suspend the alert of an hour.
    2. Click OK.

    The alert is suspended for 60 minutes and you are listed as the owner in the alert list. If it is not resolved in an hour, it returns to an active state.

  7. Select the row that contains the Cluster has many Virtual Machines that have memory contention due to memory compression, ballooning or swapping alert and click Cancel to remove the alert from the list.

    This alert is a known problem that you cannot resolve until the new hardware arrives.

    The alert is removed from the alert list, but the underlying condition is not resolved by this action. The symptoms in this alert are based on metrics, so the alert will be generated during the next collection and analysis cycle. This pattern continues until you resolve the underlying hardware and workload distribution issues.

Results

You processed the critical health alerts and took ownership of the ones to resolve or troubleshoot further.

What to do next

Respond to an alert. See User Scenario: Respond to a vRealize Operations Manager Alert in the Health Alert List.