If you're using any of the vRealize Suite Cloud offerings, you are running Cloud Proxies (CP) in your Private Cloud. These sit in your on-prem Datacenter and act as the gateway from the Cloud into your environment.
Each of the vRealize Suite Cloud offerings (vROps, vRLI, vRA, and vRNI) has its own CP (or Collector VM in the case of vRNI), we will focus on the vRLI CP here, but let's take a step back and consider all of them first. A standard deployment might look something like this.
vROps CP documentation can be found here. vROps CP sizings can be found here. They can be grouped together in a Collector Group such that vROps will spread workload across the CPs in that group, documentation can be found here.
vRA CP documentation can be found here.
vRNI Collector VM documentation can be found here.
vRLI CP documentation can be found here. All vRLI CPs will have 4 vCPU and 12GB RAM. Internal to the CP is a Log Forwarder (LF) which does most of the work. A more detailed look at the architecture above focusing on vRLI Cloud looks like this.
The LF has vCPU and RAM allocated to it from the CP, the standard allocation for the LF is 1 vCPU and 1GB RAM. LF sizing documentation can be found here.
For a higher throughput, contact VMware Cloud Services to modify the LF resources. Generally, we will want the CP to have at least 2 vCPU and 2GB RAM more than the LF. The largest LF being 8 vCPU x 16GB RAM, which requires a 10 vCPU x 18GB RAM CP.
Unlike vROps, there is no Collector Group for vRLI CPs, so you must manually spread your log sources across your CPs.
For more information on vRLI Cloud go here. Another really good resource if VMware Senior Technical Staff Member Munishpal Makhija's blog.