Another new feature in the Log Insight 2.0 beta is dashboard filters. What are dashboard filters, how do you create them, and how do they impact content packs? These are the questions I will answer in this post!
After covering the new scale-out and Windows agent features available in the Log Insight 2.0 beta, it is important to understand how to load balance traffic across a Log Insight cluster. I will cover why using a load balancer is important, what to consider when load balancing, high-level load balancer configuration, and how to balance load for the three primary ways to get data into Log Insight.
As you probably know, Windows does not natively support syslog. Several third party syslog agents exist for Windows, but each come with a list of pros and cons (for examples see this post). In addition, getting support for a Window agent can be costly. To address these limitations, Log Insight has introduced a Windows agent. I would like to walk you through how to install and configure the agent.
Less than three months since the announcement of Log Insight 1.5 GA and VMware has announced Log Insight 2.0 Beta. With the beta comes a lot of new features. Over the new few weeks, I will be diving into the new features, but today I want to highlight the important parts of the release notes.
Now that the basic components of Log Insight are known, I would like to cover the evolution of Log Insight topologies as well as the high availability. Read on to learn more!
In the last 18 months, Log Insight has released 4 GA versions, 8 TP versions (including beta), and 1 patch version (applicable to 1.5 and 2.0). Also during this time, the upgrade procedure has evolved starting with a CLI RPM upgrade in 1.0, switching to a GUI RPM upgrade in 1.5 TP2, and finally switching to a GUI PAK upgrade for 1.5 GA. In Log Insight 2.0, clustering was introduced and this increased the upgrade procedure by adding the requirement to upgrade workers. Finally, there are upgrade dependencies that must be followed. In order to make upgrades easier to understand, I would like to break it down into supported upgrade paths and supported upgrade procedures.