VMware Aria Operations (SaaS) Sizing Guidelines

Products

• VMware Aria Suite

Issue/Introduction

This article provides information on using the sizing guidelines for VMware Aria Operations (SaaS) (formerly known as vRealize Operations Cloud), to determine the configurations used during installation, or post install for cloud proxy instances.

Resolution

By default, VMware offers Standard and Small configurations during installation. You can size your cloud proxies according to the existing infrastructure to be monitored. After the VMware Aria Operations (SaaS) Cloud Proxy instance outgrows the existing size, you can either scale up your proxy instance or add more proxies to your environment.
 

	Cloud Proxy
	Small	Standard
Configuration
vCPU	2	4
Memory (GB)	8	32
Maximum number of Cloud Proxies	1000
vCPU: physical core ration (*)	1 vCPU to 1 physical core at scale maximums
Network latency (**)	< 500 ms
Network packet loss (**)	< 2%
Objects and Metrics
Maximum Objects (***)	8,000	40,000
Maximum Collected Metrics (***)	1,200,000	6,000,000
Maximum Objects with near real-time monitoring(***)	2,000	10,000
Maximum Collected Metrics with near real-time monitoring(***)	300,000	1,500,000
VMware Aria Application monitoring (telegraf) agents (****)
Maximum number of agents per node	500	3,000
Bandwidth (*****)
Minimum required (Mbps)	15	60

   * It is critical to allocate enough CPU for environments running at scale maximums to avoid performance degradation.
   ** Network requirements are for North-bound internet connectivity from Cloud Proxy to VMware Aria Operations (SaaS) hosted in AWS US West-2 Region.
  *** This is the total number of objects/metrics from all adapter instances.
 **** VMware Aria Application monitoring (telegraf) agents run on Virtual Machines and collect run-time metrics of the operating system and applications.
***** Bandwidth minimum required numbers are provided for cloud proxies working at their respective maximum sizings.
 

Near real-time monitoring

• With VMware Aria Operations (SaaS), you can collect data in near real-time from vCenter & VMware cloud on AWS.
• Cloud proxy is a key component that is used here to collect data at a higher granularity from these end-points.
• For optimal near real-time collection, size the cloud proxy with the above mentioned considerations.
   

Important Notes

• CPU and Memory configurations can both be doubled to achieve higher collecting objects and metrics.
  • A vCenter may exceed the supported objects/metrics which are supported by Cloud Proxies, thus the CPU/Memory configuration can be doubled to cover the demand.
  • Example: If a vCenter Server has 12,000 objects then a Small configuration Cloud Proxy can have it’s CPU and Memory doubled to 4 vCPUs and 16 GB RAM to support those objects.
• The number objects and metrics collected by the VMware Aria Application Monitoring (telegraf) agents should be within the supported maximum limits.
  • Each telegraf agent may collect many objects and metrics directly depending on the services running on the Operating System.
  • Example: 100 Linux Virtual Machines which have Apache Tomcat configured on them will each bring 10 additional objects adding 1000 objects to the overall count alongside the vCenter objects.