When you configure VMware Aria Operations for Logs, you must stay at or below the supported maximums.
Item | Maximum |
---|---|
Node Configuration | |
CPU | 16 vCPUs |
Memory | 32 GB |
Note: For more information on vertical scaling in
VMware Aria Operations for Logs for CPU and Memory node configurations, see
KB 332393
|
|
Storage device (vmdk) | 2 TB - 512 bytes |
Total addressable storage | 4 TB (+ OS drive) A maximum of 4 TB addressable log storage on Virtual Machine Disks (VMDKs) with a maximum size of 2 TB each. You can have two 2 TB VMDKs or four 1 TB VMDKs, and so on. When you reach the maximum, you must scale outward with a larger cluster size instead of adding more disks to existing VMs. |
Syslog connections | 750 |
Cluster Configuration | |
Nodes | 18 (Primary + 17 Workers) |
Virtual IP addresses | 60 |
Ingestion per Node | |
Events per second | 15,000 eps |
Syslog message length | 10 KB (text field) |
Ingestion API HTTP POST request | 16 KB (text field); 4 MB per HTTP Post request |
Integrations | |
VMware Aria Operations | 1 |
vSphere | 15 per node |
VMware SSO | 1 |
Active Directory domains | 1 |
Email servers | 1 |
DNS servers | 2 |
NTP servers | 4 |
Forwarders |
10
Note: From
VMware Aria Operations for Logs version 8.18 and above, you can increase the number of Log Forwarders. For more information, see
KB 376529.
|
Index Partition Configuration | |
Index partitions | 10 |
You can use the VMware Aria Operations for Logs Sizing calculator to determine sizing for VMware Aria Operations for Logs and network and storage use. This calculator is intended for guidance only. Many environment inputs are site-specific, so the calculator necessarily uses estimations in some areas. See https://vrlisizer.vmware.com.