Sizing and Scaling CPU, Memory and Storage VCF Operations for Logs 9.1

Sizing the Log Management nodes upfront can be difficult without knowing Events per Second (EPS). In order to do an initial sizing of VCF Operations for Logs, I would recommend using best estimates and consulting the sizing guides found in Broadcom's documentation as well as the VCF Operations Size Estimator. Base your initial CPU/Memory node size off of your number of hosts and then use an estimate of Events Per Second and retention period to determine storage size. Here is a chart for reference:

The sizing is based on the following assumptions.

• Each virtual CPU is at least 2 GHz.

• Each ESXi host sends up to 10 messages per second with an average message size of 170 bytes/message, which is roughly equivalent to 150 MB per day, per host.

If we are assuming about 150 MB per day per host, then we can calculate the storage requirements using the following formula: Storage in TB = (150 MB/ 1 day/ 1 host) x (Number of Hosts) x (Number of Days) x (1 TB/1000000 MB)

Once you have deployed your Logs nodes, you can scale them up as needed by going into Build > Lifecycle > VCF Management > Log Management From here click on Actions and then Scale or Increase Storage Size depending on your bottleneck:

In order to determine bottlenecks, such as storage capacity or EPS, we can use the built in dashboards:

I have found the Log Management Health Overview and Log Management Health Drilldown dashboards to be uniquely helpful when determining EPS, Gb per day, and Current Capacity utilization. Log Management Health Overview is good for seeing EPS and is available OOTB. Log Management Health Drilldown is good for seeing storage, CPU, and Memory demands vs capacity, however this dashboard needs to be activated. Simply keyword search the dashboard under Operate > Dashboards > Manage and you will see that it is inactive. Press the ellipses and hit Activate.

Hope this helps!