As I covered in the past, Log can be licensed per OSI or CPU. If you are using OSI licensing for ESXi then you may notice the same hosts are counted more than once. In this post, I will cover how to fix this issue. 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!
I cannot remember the last time I burned a CD or DVD. I can remember the last time I attempted to create a bootable USB device from an ISO. Unfortunately, I have memories of wasting time creating bootable USB devices as well. In this post I will discuss how to use UNetbootin to make creating bootable USB devices easy.
Now that you know about the new RBAC feature available in Log Insight 2.5, I would like to walk you through an example on how to configure RBAC with real data.
I frequently get questions around how to forward only certain log files from ESXi or how to collect a log file that is missing. I get the question so frequently that it warrants a quick post. The title of this post says it all – it’s all or nothing. If you configure remote syslog on ESXi then you will get all configured logs files from ESXi. There is no supported way today to customize what logs files are stored locally versus sent remotely. The only customization that you can make is what severity logs messages are forwarded to the remote syslog destinations by changing log verbosity, however this is not recommended (read here for more information).
In case you missed it, William Lam recently put up a couple of excellent posts on how to configure some important vCenter Server alarms. As it turns out, the underlying VOB (VMkernel Observation) messages appear in vSphere logs and if your are running Log Insight you can easily check for environmental issues such as the ones he outlined.
A long time ago, I talked about an internal error messages I received on ESXi. The workaround was to reboot the ESXi host, which is not the best outcome in my opinion. Recently, I hit this issue again, but this time specific to trying to configure remote syslog. I saw this issue will configuring vSphere integration on Log Insight and would like walk through the steps I took to address the issue.