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 sized so as to accommodate the SDDC design by deploying the following management packs:

Management Pack for VMware vCenter Server (installed by default)

Management Pack for NSX for vSphere

Management Pack for Storage Devices

Management Pack for vRealize Log Insight (installed by default)

Management Pack for vRealize Automation

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

Initial Setup

Scaled 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

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 grows, you should deploy more data notes to accommodate the larger expected number of objects and metrics. Consider deploying additional vRealize Operations Manager data notes only if more ESXi hosts are added to the management pods to guarantee that the vSphere cluster has enough capacity to host these additional nodes without violating the vSphere DRS anti-affinity rules.

Size of a Medium vRealize Operations Manager Virtual Appliance

Attribute

Specification

Appliance size

Medium

vCPU

8

Memory

32 GB

Single-Node Maximum Objects

7,000

Single-Node Maximum Collected Metrics (*)

2,000,000

Multi-Node Maximum Objects Per Node (**)

5,000

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

1,500,000

Maximum number of End Point Operations Management agents per node

1,200

(*) 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 get the number of metrics collected by each adapter instance. The sum of these metrics is what is estimated in this sheet.

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.

Analytics Cluster Node Size Design Decision

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-MON-003

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 a lower number of 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.

Hypervisor hosts used in the management cluster must have physical CPU processor with a minimum of 8 cores per socket. In total this will utilize 24 vCPUs and 96 GB of memory in the management cluster.

SDDC-OPS-MON-004

Initially deploy 3 medium-size nodes for the first 1,000 virtual machines in the compute pod.

Provides enough capacity for the metrics and objects generated by 100 hosts and 1,000 virtual machines while having high availability enabled within the analytics cluster.

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 spread this load out more evenly.

SDDC-OPS-MON-005

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

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

For example, if the management 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 up to 10,000 virtual machines.

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

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

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

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.

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.

Configuration and Resources Requirements of the Remote Collector Nodes Design Decision

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-MON-006

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.