Events, tasks, and alerts are structured data with specific meaning. You can configure VMware Aria Operations for Logs (SaaS) to collect alarms, events, and tasks data from one or more vCenter Server systems.

You use the VMware Aria Operations for Logs (SaaS) interface to configure VMware Aria Operations for Logs (SaaS) to connect to vCenter Server systems. The information is pulled from the vCenter Server systems by using the vSphere Web Services API and appears as a vSphere content pack in the VMware Aria Operations for Logs (SaaS) web user interface.

Note: VMware Aria Operations for Logs (SaaS) can pull alarms, events, and tasks data only from vCenter Server 5.5 and later.

Prerequisites

  • Verify that the vCenter Server that manages the ESXi host is registered with your VMware Aria Operations for Logs (SaaS) service. Or, you can register the ESXi host and configure vCenter Server in a single operation.
  • In vSphere, verify that you have user credentials with System.View privileges.
    Note: You must configure the permission on the top-level folder within the vCenter Server inventory, and verify that the Propagate to children check box is selected.

  • Verify that you are logged in to the VMware Aria Operations for Logs (SaaS) web user interface as an administrator.

Procedure

  1. Click the two arrows icon in the upper-left corner of the screen to expand the main menu.
  2. Navigate to Configuration > vSphere Integration.
  3. Locate the vCenter Server instance from which you want to collect data, and click the instance.
  4. Select the Collect vCenter Server events, tasks, and alarms check box.
  5. Click Save.

Results

The Cloud Proxy connects to the vCenter Server every two minutes and ingests all new information since the last successful poll. The events, tasks, and alarms of the vCenter Server instance are sent to VMware Aria Operations for Logs (SaaS) and show up as searchable events in the Explore Logs page. However, vCenter Server logs must be sent separately via a VMware Aria Operations for Logs Agent.

Important:

The Cloud Proxy is deprecated. You can continue to use your existing Cloud Proxy configurations, but there will be no new feature updates to the Cloud Proxy.

What to do next

  • Analyze vSphere events using the vSphere content pack or custom queries.
  • Enable vSphere content pack alerts or custom alerts.