On a recent, fresh installation of LogInsight I observed that no data from a set of hosts was coming into the LogInsight server.
Debugging showed not issues related to the usual suspects of DNS, NTP, firewall or network which left me a bit puzzled.
I found the answer by going through the logs of the loginsight agent (usually in /var/log/loginsight-agent/liagent_<date>):
Wow, what a day:
Today I have received the Germany FY22/Q1 EPIC2 award at VMware for “Integrity”!
Tagging the vCenter (object)
Today I learned...
I am working on enhancing my vSphere release tagging script with the ability to tag the vCenter with a human-readable release name. As shown in the screenshot, it’s easy enough in the UI.
Tagging ESXi hosts with canonical release names
Save some time looking up build numbers
Update [2021-03-09] The repository has been renamed to VMware-vSphere-Release-Tagging as the future scope should include the vCenter as well. Thank you for all the feedback!
Providing machine readable VMware release data
Get VMware product release data ready for automation
I started a project with the goal to re-format VMware product release information in a way that can be used in automation and scripting. These days, even Excel can handle JSON. When searching for new projects I often need some external trigger to take the first step. In this case, a customer I have been working gave me the reason to do something (thanks, Tim!).
