The foundation of vRealize Operations Manager is a single instance of a 3-node analytics cluster that is deployed in the hub of the SDDC, and a 2-node remote collector cluster in each ROBO.

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.

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.

The vRealize Operations Manager analytics cluster design is covered in the VMware Validated Design for SDDC.

Figure 1. Logical Design of vRealize Operations Manager ROBO Deployment

Logical Design of vRealize Operations Manager ROBO Deployment

Physical Design

The vRealize Operations Manager analytics cluster and remote collector nodes run on the management pod in hub and the remote collector nodes run on the Consolidated cluster in the ROBO. For information about the types of pods, see Pod Architecture.

Data Sources

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

  • Consolidated pod

    • vCenter Server

    • ESXi hosts

  • NSX for vSphere

    • NSX Manager

    • NSX Controller Instances

    • NSX Edge instances

  • vRealize Automation‚Ä®

    • vRealize Agent Servers

  • vRealize Log Insight