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 ROBO 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(*)

1,500

Single-Node Maximum Collected Metrics

600,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 Maximum

N/A

Maximum Metrics for 16-Node Configuration

N/A

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

Table 2. Configuration and Resources Requirements of the Remote Collector Nodes Design Decision

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-OPS-MON-002

Deploy the standard-size remote collector virtual appliances.

Enables metric collection for the expected number of objects in the SDDC when at full capacity.

You must provide 4 vCPUs and 8 GB of memory in the Consolidated cluster in each ROBO.