vRealize Operations Manager communicates with the management components of the SDDC to collect metrics which are presented through a number of dashboards and views.

Logical Design

In the consolidated SDDC, you deploy a vRealize Operations Manager configuration that consists of the following entities.

  • 1-node (medium-size) vRealize Operations Manager analytics cluster. This topology provides the ability to add high availability, scale-out capacity up to sixteen nodes, and failover.

  • 1 standard remote collector node. The remote collectors communicate directly with the vRealize Operations Manager analytics cluster. The design uses remote collectors whose role is to ease scalability by performing the data collection for localized applications and periodically sending collected data to the analytics cluster.

Figure 1. Logical Design of vRealize Operations Manager

vRealize Operations Manager deployment include an analytics cluster and a remote collector cluster. You monitor all SDDC management products that are used in this VMware Validated Design.

Physical Design

The vRealize Operations Manager nodes run on the consolidated pod. For information about the types of pods, see Pod Types for Consolidated SDDC.

Data Sources

vRealize Operations Manager collects data from the following virtual infrastructure and cloud management components.

  • Virtual Infrastructure

    • Platform Services Controller

    • vCenter Server

    • ESXi hosts

    • NSX Manager

    • NSX Controller Instances

    • NSX Edge Services Gateway instances

    • Shared storage

  • vRealize Automation

    • vRealize Automation Appliance

    • vRealize IaaS Web Server

    • vRealize IaaS Management Server

    • vRealize IaaS DEM

    • vRealize Agent Servers

    • Microsoft SQL Server

  • vRealize Business for Cloud

  • vRealize Log Insight

  • vRealize Operations Manager