In addition to configuration maximums, it is important to understand configuration minimums. Again, most of this information is in the official documentation, but is not consolidated in a central location… until now!
UPDATE: Configuration minimums have been added to the Log Insight documentation starting with 3.0. This information may be out of date — please use the official documentation!
I have received many requests for Log Insight configuration maximums. While most of the relevant information is available in the official documentation, there is no central place to reference… until now!
UPDATE: Configuration maximums have been added to the Log Insight documentation starting with 3.0. This information may be out of date — please use the official documentation!
I have covered Log Insight reference architectures in the past, but I have received a few inquiries about large Log Insight deployments. In this post, I will cover a variety of different large Log Insight deployments and the reference architecture information you need to know. Read on to learn more!
I am happy to announce the release of Log Insight 3.6. As always, this release has a ton of new features. Read on to learn more!
The second agent parser I want to take a look at is the KVP parser. Read to learn how it works!
One of the great improvements in Log Insight 3.0 is around scale and more specifically its ingestion rate, cluster size and retention period. In this post, I would like to discuss this improvement as well as how to properly calculate Log Insight cluster deployments for 3.0.
In Log Insight 2.0 a clustering feature was introduced. This feature made it possible to go above the configuration maximums of a single node, however scale is not the only reason to consider when architecting a Log Insight solution and considering clustering. In this post, I would like to discuss other benefits to leveraging a cluster.
In Log Insight 2.0 a scale-out feature was introduced. The best practice when using scale-out is to configure an external load balancer in front of the cluster and send all ingestion traffic (i.e. syslog and ingestion API) to the load balancer instead of directly to a node. The reason for this best practice is to assist with balancing data across nodes and also to provide ingestion high availability. In this post, I would like to discuss why data may not be balanced across a Log Insight cluster whether a load balancer is used or not.
This page contains the most relevant information for VMware Log Insight! Official links Product Page – information about Log Insight, trial/download, purchasing, and other…
Can't find what you're looking for? Try refining your search:
