One of the great features of Log Insight is its tight integration with other VMware products. One of these integrations is with vSphere. I have talked about vSphere integration in the past, however I would like to do so in more details to clear up some questions I have received lately.
Here it is, the blog post you have all been waiting for — Log Intelligence versus Log Insight. Well, actually it is Log Intelligence and Log Insight.The post will answer why two products with two different names. Read on to learn more! versus
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!
As you probably know, the Log Insight virtual appliance relies on OVF properties to handle some amount of configuration. OVF properties are powerful in that they can be set at deploy time, changed at a later time, and can be used instead of relying on a CLI or needing to write a UI on top of a CLI. With that said, OVF properties have two significant limitations:
They require vSphere — not an issue for Log Insight as it is only available as a virtual appliance
They can go missing
The issue of missing OVF properties is what I would like to cover in this post. Read on to learn more!
From time to time, I hear about the desire to configure two separate Log Insight instances to forward to one another without creating a loop. In this post, I will discuss the reasons for this desired state, the best practice to achieve this desired state and some alternatives to consider. Read on to learn more!
In my last post, I talked about the now supported VIDM integration in Log Insight. One thing I mentioned was the impact VIDM has versus LI instances with existing AD accounts. In this post, I would like to dig into the details. Read on to learn more!
Log Insight has featured a Tech Preview of VMware Identity Manager (VIDM) integration for the last two releases. I am happy to announce that as of Log Insight 4.3, this feature is now fully supported. Read on to learn more!
The Log Insight team takes customer experience seriously. As you know, there is a public community where you can submit and vote for features requests. The number one feature was vSphere datastore ID to name aliasing. I am happy to announce it has been implemented in Log Insight 4.0. Read on to learn more!