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!
Someone recently pinged me stating that a group that had been defined on the Access Control page of Log Insight was grayed out. They wanted to know why and how to fix it. Read on to learn more!
Log Insight has always shipped with the General and vSphere content packs. Several enhancements have been made to these content pack in version 4.5. In addition, more content packs are now included out of the box. Read on to learn more!
I covered the datastore ID to name aliasing feature in Log Insight 4.0, but under the covers is really a more generic aliasing feature that has not been exposed yet. I walked though a bit of how the aliasing feature works, but I wanted to dig a little deeper into the aliasRules option. Read on to learn more!