When a worker is put into maintenance mode it can be done safely without loss of log ingestion. The ILB allows log ingestion to be balanced across worker nodes in a LI cluster. In this case the current Master node is 192.168.110.100. The VIP takes the L2 MAC of the current master and acts as a proxy. It is also found through the FQDN of l DNS entry. The ILB here is enabled on the IP address of 192.168.110.99. The image below highlights the sources of how my Log Insight cluster is set up. ILB and ELB allow logs to continue to be ingested when a worker or node become unavailable. Workers take logs in from the External Load Balancer (ELB) or Integrated Load Balancer (ILB). The master is the active node in which lookups are performed against. Whilst you can have a stand alone server processing logs, if you require high log ingest then you need to have additional workers. The architecture of Log Insight is clustered in nature. This has been traditionally been solved with an external load balancer. Keeping the logging service up and running is important. Ingestion, RegEx and search, and awesome visualisation. Coming from an ELK background there is a sense of familiarity here. The Log Insight log appliance from VMware allows the ingestion of many logs. With the importance of logging on the increase you need to ensure you have a distributed log management system that can ingest thousands, if not hundreds of thousands of inputs per second.

Inferno unitool loader