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!
Not that I think you should ever remove Log Insight from your environment, but I have been asked how to properly remove Log Insight (e.g. re-purposing an environment) after it has been configured. Read on to learn more!
While Log Insight strives to make administration easy, issues may be experienced from time-to-time. On rare occasion, I have heard of a Log Insight upgrade failing. The question becomes what should you do if the upgrade fails? Read on to learn more!
Someone approached me recently with the following question:
I am in the process of integrating vIDM with Log Insight and have a business requirement that vIDM be highly available. Currently, the conceptual design is looking like a 2-node cluster behind a NSX based LB. I will not have more than 15 – 20 admins using vRLI, and I’m therefore wondering if the design requires an external SQL database or not?
What is my recommendation? Read on to learn more!