Configure your initial deployment of vRealize Operations Manager based on the anticipated use.

Analytics Nodes

Analytics nodes consist of a primary node, a primary replica node, and data nodes.

For enterprise deployments of vRealize Operations Manager, deploy all nodes as medium, large or extra-large deployments, depending on sizing requirements and your available resources.
Scaling Vertically by Adding Resources
If you deploy analytics nodes in a configuration other than large, you can reconfigure the vCPU and memory. It is recommended to scale up the analytics nodes in the cluster before scaling out the cluster with additional nodes. vRealize Operations Manager supports various node sizes.
Table 1. Analytics Nodes Deployment Sizes
Node Size vCPU Memory
Extra small 2 8 GB
Small 4 16 GB
Medium 8 32 GB
Large 16 48 GB
Extra large 24 128 GB
Scaling Vertically by Increasing Storage
You can increase storage independently of vCPU and Memory.
To maintain a supported configuration, data nodes deployed in the cluster must be the same node size.
For more information about increasing storage, see the topic, Add Data Disk Space to a vRealize Operations Manager vApp Node. You cannot modify the disks of virtual machines that have a snapshot. You must remove all snapshots before you increase the disk size.
Scaling Horizontally (Adding nodes)
vRealize Operations Manager supports up to eight extra-large analytics nodes in a cluster, or up to 10 extra-large nodes in a cluster when continuous availability is enabled.
To maintain a supported configuration, analytics nodes deployed in the cluster must be the same node size.
Witness Node
vRealize Operations Manager provides a single size regardless of the cluster size since the witness node does not collect nor process data.
Table 2. Witness Node Deployment Sizes
Node Size vCPU Memory
Witness 2 8 GB
Remote Collectors
vRealize Operations Manager supports two sizes for remote collectors, standard and large. The maximum number of resources is based on the aggregate resources that are collected for all adapters on the remote collector. In large scale vRealize Operations Manager monitored environment, you might experience a slow responding UI, and metrics are slow to be displayed. Determine the areas of the environment in which the latency is greater than 20 milliseconds and install a remote collector in those areas.
Table 3. Supported Remote Collector Sizes
Collector Size Resources End Point Operations Management Agents
Standard 6000 250
Large 32,000 2,000
For more information about sizing, see the KB article vRealize Operations Manager Sizing Guidelines (KB 2093783).
vRealize Application Remote Collector
vRealize Operations Manager supports three sizes for application remote collectors; small, medium, and large. The number of Telegraf agents you want to deploy determines the size of vRealize Application Remote Collector you deploy.

Currently, vRealize Application Remote Collector can collect data on 20 different application sources.

If you have more than 6,000 Telegraf agents installed, increase vCPU and memory of the large configurations so that you can monitor up to 10,000 Telegraf agents.

An increase of memory usage depends on the number of services and their configurations on the VMs that are being monitored. When you monitor 1000 operating system objects, memory usage increases by around 1-1.5 GB.
Table 4. Supported vRealize Application Remote Collector Sizes
vRealize Application Remote Collector Size Maximum number of Telegraf Agents Supported
Small 500
Medium 3000
Large 6000