Log Insight has been around for many years now and the product is always evolving. I recently was asked to assist with a Log Insight instance running internally and when I logged into the UI I almost did not recognize the product. This was because the instance was running an old version of Log Insight. Based on this, I thought it would be cool to show how the UI has evolved over time. Read on to learn more!
As you probably know, non-content pack alerts are owned by users. The question becomes, what happens if a user who has alerts leaves the company? Put another way, how do you change the ownership of user alerts? Read on to learn more!
Did you know Log Insight has the notion of a master node and a leader node? Do you know the differences about the roles? Read on to learn more!
Log Insight 4.5 added some nice enhancements around alerts. I would like to cover all the enhancements in this post. Read on to learn more!
When deploying Log Insight, you have the option of selecting various deployment sizes. By default, Log Insight defaults to small. The best practice for production workloads is to deploy at least medium and whenever possible large. You will notice that by default and even with the larger deployment sizes that Log Insight allocates just over 500GB of space. In general, 500GB is not a lot of space for events and for production environments you will often need more space. With that said, some environments are small and do not require this amount of space/retention. One question I am asked is how to deploy Log Insight with less than 500GB of space. Read on to learn more!
I often get asked for specific examples on how Log Insight is / can be used to root cause an issue. I recently had an issue in my homelab that impacted my vCenter. In this post, I will cover the value Log Insight provided and how I was able to reach a root cause. Read on to learn more!
Since the Log Insight Agent was introduced, it has supported silent installation options to assist in automated deployments. The silent installation options were primarily focused around server, port, and protocol specifications. With the change of enabling SSL by default in Log Insight 4.0, additional parameters became necessary to automate the deployment of the agent in all environments. In addition, there have been feature requests to control other aspects of the agent during installation. In version 4.5, additional parameters were introduced to provide the flexibility you need. Read on to learn more!