If you are running multiple Log Insight instances or manage a Log Insight cluster you may be looking for a way to automate upgrades. Read on to learn a couple ways to achieve this today.
Log Insight 2.0 introduced the ability to scale-out in addition to scale-up. With this change, a Log Insight instance is capable of playing different roles or service types. These include:
- Standalone (available in 1.x)
- Master (new in 2.0)
- Worker (new in 2.0)
NOTE: Service types should not be confused with node types. Every Log Insight instance (or node) is capable of running any service it is matter of what service is enabled on the node.
I would like to discuss the differences between these service types and some important considerations to keep in mind.
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 just wanted to make people aware of a new VMware Knowledge Base (KB) article that has been published regarding Log Insight 2.0.
Continuing with my video theme, I have a video going through the initial configuration wizard of Log Insight 2.0 when attempting to create a standalone instance.
For those interested in deploying Log Insight 2.0 for the first time, setting up a new Log Insight instance, or creating a Log Insight cluster, this video is for you!