VMware ESXi logs internally to a ramdisk. If configured, the host also logs to a persistent scratch location on disk or to a remote syslog server via the network. Persistent logging survives across reboots of an ESXi host, and is important for troubleshooting.
This articles provides guidance for determining whether an ESXi host has been configured for persistent logging. It also points to documentation or other articles for changing that configuration.
VMware ESXi 8.x
VMware ESXi 7.x
VMware ESXi 6.x
If an ESXi host has been configured to store logs on a persistent disk or to send them to a remote syslog server via the network, those logs are considered persistent.
VMware ESXi hosts can be configured to ship logs remotely to a syslog server for long-term storage. The ESXi host cannot guarantee that the remote syslog server is retaining these logs according to any given retention policy.
Check the configuration of the ESXi host's syslog service as there are multiple configuration options available depending on the version of ESX or ESXi you are running:
VMware ESXi hosts can be configured to copy logs to a local disk device for long-term storage. The ESXi host controls the rotation and retention of these logs.
Check the configuration of the ESXi host's syslog service. The host should be configured with a persistent location on disk to store the logs:
To validate that the target is receiving information:
esxcli system syslog mark --message "Syslog Test Message"
logger -t vmkernel "Syslog Test Message"