Logical and Physical Design of vRealize Operations Manager in ROBO

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

Logical Design

You deploy a vRealize Operations Manager configuration that consists of the following entities.

• 3-node (medium-size) vRealize Operations Manager analytics cluster that is highly available (HA) in the hub. This topology provides high availability, scale-out capacity up to sixteen nodes, and failover.

• 2 remote collector nodes in each ROBO. The remote collectors communicate directly with the data nodes in the vRealize Operations Manager analytics cluster. For high availability and fault tolerance, two remote collectors are deployed in each ROBO.

Figure 1. Logical Design of a Multi-Region Deployment of vRealize Operations Manager in the Hub

Figure 2. Logical Design of vRealize Operations Manager in ROBO

Each ROBO contains its own pair of remote collectors whose role is to ease scalability by performing the data collection from the applications and periodically sending collected data to the analytics cluster.

For information about the vRealize Operations Manager analytics cluster design, see VMware Validated Design for Software-Defined Data Center.

Physical Design

The vRealize Operations Manager nodes run on the . For information about the types of clusters, see Workload Domain Architecture in ROBO.

Data Sources

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

• Virtual Infrastructure

  • vCenter Server with embedded Platform Services Controller

  • ESXi hosts

  • NSX Manager

  • NSX Controller instances

  • NSX Edges

  • Shared storage

• vRealize Automation

  • vRealize IaaS Proxy Agents

• vRealize Business for Cloud

  • vRealize Business Data Collector

• vRealize Log Insight