vRealize Operations Manager communicates with all management components in both regions of the SDDC to collect metrics which are presented through a number of dashboards and views.
In a multi-region SDDC, 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). This topology provides high availability, scale-out capacity up to sixteen nodes, and failover.
2 remote collector nodes in each region. The remote collectors communicate directly with the data nodes in the vRealize Operations Manager analytics cluster. For load balancing and fault tolerance, two remote collectors are deployed in each region.
Each region contains its own pair of remote collectors whose role is to ease scalability by performing the data collection from the applications that are not subject to failover and periodically sending collected data to the analytics cluster. You fail over the analytics cluster only because the analytics cluster is the construct that analyzes and stores monitoring data. This configuration supports failover of the analytics cluster by using Site Recovery Manager. In the event of a disaster, Site Recovery Manager migrates the analytics cluster nodes to the failover region.
The vRealize Operations Manager nodes run on the management pod in each region of SDDC. For information about the types of pods, see Pod Architecture.
vRealize Operations Manager collects data from the following virtual infrastructure and cloud management components.
Platform Services Controller instances
vCenter Server instances
NSX Manager instances
NSX Controller instances
NSX Edge instances
vRealize Automation Appliance
vRealize IaaS Web Server
vRealize IaaS Management Server
vRealize IaaS DEM
vRealize vSphere Proxy Agents
Microsoft SQL Server
vRealize Business for Cloud
vRealize Log Insight
vRealize Operations Manager