Sizing Compute Resources for vRealize Operations Manager in ROBO

You size compute resources for vRealize Operations Manager to provide enough resources to run the remote collectors in each ROBO.

Sizing Compute Resources for the Remote Collector Nodes

Unlike the analytics cluster nodes, remote collector nodes have only the collector role. Deploying two remote collector nodes in each region does not increase the capacity for monitored objects.

Table 1. Size of a Standard Remote Collector Virtual Appliance for vRealize Operations Manager

Attribute	Specification
Appliance size	Remote Collector - Standard
vCPU	2
Memory	4 GB
Single-Node Maximum Objects	6,000
Single-Node Maximum Collected Metrics (*)	1,200,000
Multi-Node Maximum Objects Per Node	N/A
Multi-Node Maximum Collected Metrics Per Node	N/A
Maximum number of End Point Operations Management agents per node	250
Maximum Objects for 16-Node Configuration	N/A
Maximum Metrics for 16-Node Configuration	N/A

*The object limit for a remote collector is based on the VMware vCenter adapter.

Table 2. Design Decisions on the Compute Size of the Remote Collector Nodes of vRealize Operations Manager

Decision ID	Design Decision	Design Justification	Design Implication
ROBO-OPS-MON-003	Deploy the standard-size remote collector virtual appliance.	Enables metric collection for the expected number of objects in the ROBO SDDC when at full capacity.	You must provide 4 vCPUs and 8 GB of memory in the consolidated cluster.