You size compute resources for vRealize Operations Manager to provide enough resources for accommodating the analytics operations for monitoring the SDDC.

Size the vRealize Operations Manager analytics cluster according to VMware Knowledge Base article 2093783. vRealize Operations Manager is also sized so as to accommodate the SDDC design by deploying a set of management packs. See Management Packs in vRealize Operations Manager for Consolidated SDDC.

The sizing of the vRealize Operations Manager analytics cluster is calculated using the following options:

Initial Setup (Up to 500 VMs) - Single Node

Scaled Out (Up to 1,000 VMs) - 3 Nodes

Scaled Out (Up to 1,500 VMs) - 4 Nodes

1 vCenter Server

1 vCenter Server

1 vCenter Server

1 NSX Manager

1 NSX Manager

1 NSX Manager

3 NSX Controllers

3 NSX Controllers

3 NSX Controllers

32 ESXi hosts

48 ESXi hosts

64 ESXi hosts

1 vSAN datastore

1 vSAN datastore

1 vSAN datastore

500 virtual machines

1,000 virtual machines

1,500 virtual machines

Sizing Compute Resources for the Analytics Cluster Nodes

Deploying one medium-size virtual appliance satisfies the initial setup for retention and for monitoring the expected number of objects and metrics for an environment up to 500 virtual machines. As the environment extends, you should deploy more nodes to accommodate the larger expected number of objects and metrics to support 1,500 virtual machines. Consider deploying additional vRealize Operations Manager nodes only if more ESXi hosts are added to the consolidated pod to guarantee that the vSphere cluster has enough capacity to host these additional nodes without violating the vSphere DRS anti-affinity rules.

Table 1. Size of a Medium vRealize Operations Manager Virtual Appliance

Attribute

Specification

Appliance size

Medium

vCPU

8

Memory

32 GB

Single-Node Maximum Objects

8,500

Single-Node Maximum Collected Metrics (*)

2,500,000

Multi-Node Maximum Objects Per Node (**)

6,250

Multi-Node Maximum Collected Metrics Per Node (**)

1,875,000

Maximum number of End Point Operations Management agents per node

1,200

Maximum Objects for 16-Node Configuration

75,000

Maximum Metrics for 16-Node Configuration

19,000,000

(*) Metric numbers reflect the total number of metrics that are collected from all adapter instances in vRealize Operations Manager. To get this number, you can navigate to the Cluster Management page in vRealize Operations Manager, and view the adapter instances of each node at the bottom of the page. You can view the number of metrics collected by each adapter instance. The sum of these metrics is what is estimated in this table.

Note:

The number shown in the overall metrics on the Cluster Management page reflects the metrics that are collected from different data sources and the metrics that vRealize Operations Manager creates.

(**) Note the reduction in maximum metrics to permit some head room.

Table 2. Design Decisions for Analytics Cluster Compute Sizing for vRealize Operations Manager

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-OPS-MON-003

Initially deploy the analytics cluster with 1 medium-size node for the first 500 virtual machines in the consolidated pod.

Provides enough capacity to accommodate the metrics and objects generated by 32 hosts and 500 virtual machines without high availability enabled in the analytics cluster and collection of metrics about the following components.

  • Consolidated vCenter Server and Platform Services Controller

  • ESXi hosts in the consolidated cluster including shared storage

  • NSX for vSphere components for the consolidated cluster

  • Cloud Management Platform components

  • vRealize Log Insight components

  • Hypervisor hosts used in the consolidated pod must have a physical CPU processor with a minimum of 8 cores per socket.

  • You must add more nodes to the analytics cluster to support 1,500 virtual machines.

CSDDC-OPS-MON-004

Add more medium-size nodes to the analytics cluster if the SDDC expands past 500 virtual machines.

The number of nodes should not exceed number of ESXi hosts in the consolidated pod - 1 .

For example, if the consolidated pod contains 6 ESXi hosts, you deploy a maximum of 5 vRealize Operations Manager nodes in the analytics cluster.

  • Ensures that the analytics cluster has enough capacity to meet the virtual machine object and metrics growth as required.

  • Ensures that the consolidated pod always has enough physical capacity to take a host offline for maintenance or other reasons.

The consolidated pod must have enough ESXi hosts so that vRealize Operations Manager can run without violating vSphere DRS anti-affinity rules.

Sizing Compute Resources for the Remote Collector Nodes

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

Table 3. 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

Maximum number of End Point Operations Management Agents per Node

250

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

Table 4. Design Decisions for Remote Collector Compute Sizing for vRealize Operations Manager

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-OPS-MON-005

Initially deploy the remote collector group with 1 standard-size remote collector node in the consolidated pod.

Offloads the metric data collection from the nodes running in the analytics cluster and provides the ability to scale out and load balance as the platform expands.

You must provide 2 vCPUs and 4 GB of memory in the consolidated pod.