You size compute resources for vRealize Operations Manager to provide enough resources for accommodating the analytics operations for monitoring the SDDC and the expected number of virtual machines in 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

The sizing of the vRealize Operations Manager instance is calculated using the following two options:

Initial Setup

Scaled-Out Setup

4 vCenter Server Appliances

4 vCenter Server Appliances

4 NSX Managers

4 NSX Managers

6 NSX Controllers

6 NSX Controllers

50 ESXi hosts

100 ESXi hosts

4 vSAN datastores

4 vSAN datastores

1,000 virtual machines

10,000 virtual machines

Sizing Compute Resources for the Analytics Cluster Nodes

Deploying 3 medium-size virtual appliances satisfies the initial requirement for retention and for monitoring the expected number of objects and metrics for smaller environments up to 1,000 virtual machines. As the environment expands, deploy more data notes to accommodate the higher expected number of objects and metrics.

Consider deploying additional vRealize Operations Manager data notes only if more ESXi hosts are added to the management cluster to guarantee that the vSphere cluster has enough capacity to host these additional nodes without violating the vSphere DRS anti-affinity rules.

Table 1. Resources for a Medium-Size 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 go 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 estimations in the specification table represent the sum of these metrics.

Note:

The number that is 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.

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

Table 2. Design Decisions on the Compute Size of the Analytics Cluster Nodes of vRealize Operations Manager

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-MON-005

Deploy each node in the analytics cluster as a medium-size appliance.

Provides the scale required to monitor the SDDC when at full capacity.

If you use fewer large-size vRealize Operations Manager nodes, you must increase the minimum host memory size to handle the increased performance that is the result from stretching NUMA node boundaries.

ESXi hosts in the management cluster must have physical CPUs with a minimum of 8 cores per socket. In total, vRealize Operations Manager uses 24 vCPUs and 96 GB of memory in the management cluster.

SDDC-OPS-MON-006

Deploy initially 3 medium-size nodes for the first 1,000 virtual machines in the shared edge and compute cluster.

Provides enough capacity for the metrics and objects generated by 100 hosts and 1,000 virtual machines while having high availability in the analytics cluster enabled and collection of metrics about the following components.

  • vCenter Server and Platform Services Controller

  • ESXi hosts

  • NSX for vSphere components

  • Cloud Management Platform components

  • vRealize Log Insight components

The first 3 medium-size nodes take more resources per 1,000 virtual machines because they have to accommodate the requirements for high availability. Nodes that are deployed next can distribute this load out more evenly.

SDDC-OPS-MON-007

Add more medium-size nodes to the analytics cluster if the number of virtual machines in the SDDC exceeds 1,000.

  • Ensures that the analytics cluster has enough capacity to meet the virtual machine object and metric growth up to 10,000 virtual machines.

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

  • The capacity of the physical ESXi hosts must be enough to accommodate virtual machines that require 32 GB RAM without bridging NUMA node boundaries.

  • The management cluster must have enough ESXi hosts so that vRealize Operations Manager can run according to vSphere DRS anti-affinity rules.

  • The number of nodes must not exceed number of ESXi hosts in the management cluster - 1.

    For example, if the management cluster contains 6 ESXi hosts, you can deploy up to 5 vRealize Operations Manager nodes in the analytics cluster.

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 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

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 4. Design Decisions on the Compute Size of the Remote Collector Nodes of vRealize Operations Manager

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-MON-008

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 management cluster in each region.