In case you missed it, VMware released Log Insight 3.3.2 last Thursday. This maintenance release supports some new license keys and addresses some security issues. Read on to learn more!
As part of the vExpert community I was let in on a little secret recently — as of the next vSphere release the C# client will NO LONGER BE AVAILABLE. Read on to learn more!
Since the announcement of the free Log Insight for vCenter Server edition I have received a lot of questions about what you can and can not do. In this post, I would like to state the facts. Read on to learn more!
If you are upgrading or have upgraded to vSphere 6.0, you should be aware of a couple syslog gotchas. These will be especially important if you are running a central logging system like vRealize Log Insight. Read on to learn more.
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 my previous post, I discussed how to configure vRA logging. In this post I would like to provide some Log Insight Linux agent configuration samples for common Linux and VMware applications. You may notice some duplication of information. I will be updating this post over time so be sure to check back from time to time!