While this is very useful, and in many cases a real learning experience, it got me thinking that these logs should be available remotely as well. Since ESXi supports, and actively encourages, the use of an external Syslog service for log file safekeeping and monitoring, shouldn’t the installation logs for ESXi also be logged externally if configured?
Thinking that I couldn’t be the first person that thought of this, I looked through the scripting section of vSphere Installation and Setup - vSphere 5.0 guide I was very surprised to see that there is no option to configure syslogging until after the installation is finished and the host configuration script(s) runs (ks.cfg).
By using a ks.cfg script you can automatically configure syslog settings, but since that happens after the installation is done, and the host is potentially rebooted, the installation logs are lost (ESXi logs are not persistent by default) unless you run something that copies them over to another location before the reboot happens.
Of course, when I asked on Twitter the Godfather of Ghetto, William Lam responded that you could always create a python script that runs after the install, before a reboot, that uploads the logs to a syslog server. While this is all fine and dandy, I would still like to have the possibility to configure a syslog server during the installation, and have the installation procedure fling all it’s log goodness at the syslog server while the installation runs.
With new features like Autodeploy being utilized, having these logs automatically gathered (without ghetto hacking the installation) in a central location sounds like a really good idea to me?
Surely, I’m not the only one? Is this something that has enough brains behind it to actually warrant a proper feature request being filed with VMware?