The vRealize Log Insight cluster consists of one master node and two worker nodes. You enable the Integrated Load Balancer (ILB) on the cluster to have vRealize Log Insight to balance incoming traffic fairly among available nodes.

vRealize Log Insight clients, using both the Web user interface, and ingestion through syslog or the Ingestion API, connect to vRealize Log Insight that the ILB addresses.

vRealize Log Insight cluster can scale out to 12 nodes, that is, one master and 11 worker nodes.

Table 1. Cluster Node Configuration Design Decision

Decision ID

Design Decision

Design Justification

Design Implication


Deploy vRealize Log Insight in a cluster configuration of 3 nodes with an integrated load balancer: one master and two worker nodes.

Provides high availability. Using the integrated load balancer simplifies the Log Insight deployment, and prevents from a single point of failure.

You must size each node identically.

If the capacity requirements for your vRealize Log Insight cluster grow, identical capacity must be added to each node.


Apply vSphere Distributed Resource Scheduler (DRS) anti-affinity rules to the vRealize Log Insight cluster components

Using DRS prevents vRealize Log Insight nodes from on the same ESXi host and thereby risking the cluster's high availability capability.

Additional configuration is required to set up anti-affinity rules.

Only a single ESXi host in the management cluster, of the four ESXi hosts, will be able to be put into maintenance mode at a time.