A Cloud Proxy receives log and event information from monitored sources and sends this information to vRealize Log Insight Cloud where it can be queried and analyzed. While configuring a Cloud Proxy, you must stay at or below the supported maximums for HTTP and syslog requests.

The default configuration for Cloud Proxy is 4 vCPUs and 12 GB RAM. You can use a Cloud Proxy for an on-premise vCenter VM instance with a lower bandwidth (up to 100 MBps). The following resource limits are applicable.
Note: The following values are for non-SSL ports. You will experience a 15% drop in throughput when you use SSL ports.
Configuration Maximum Number of Log Filter Rules with Filter at Source Maximums for HTTP Requests Maximums for Syslog TCP Requests
1 CPU; 1 GB memory 5

1400 requests per second

or 20 MBps

10,500 messages per second

or 3.2 MBps

2 CPUs; 4 GB memory 10

2500 requests per second

or 48 MBps

17,700 messages per second

or 5.4 MBps

4 CPUs; 8 GB memory 20

3800 requests per second

or 63 MBps

36,000 messages per second

or 11 MBps

8 CPUs, 16 GB memory 30

5900 requests per second

or 100 MBps

75,000 messages per second

or 26 MBps

  • For a configuration of 4 CPUs and 8 GB memory, increase the Cloud Proxy configuration to at least 6 CPUs and 12 GB memory.
  • For a configuration of 8 CPUs and 16 GB memory, increase the Cloud Proxy configuration to at least 10 CPUs and 18 GB memory.
  • If you activate log filter rules with filter at source enabled, you might observe up to a 30% drop in throughput. For example, if you are using a non-SSL 1 CPU and 1 GB memory configuration, vRealize Log Insight Cloud suppports 1400 requests per second or 20 MBps. For this configuration, activating up to 5 log filter rules results in a 30% drop in throughput, which translates to 1000 requests per second or 14 MBps. In this situation, you can upgrade your configuration to maintain the throughput.