This article explains the vSAN trace-level logging and the options to configure vSAN traces.
For vSAN 6.2 and later, some of the trace-level logging created by vSAN can be forwarded to a syslog server. The total volume of traces is too great for syslog handling, but the urgent traces (provides details on most potentially-significant problems) can be forwarded to an external syslog collector. The use of syslog redirection for the urgent traces is a useful troubleshooting tool, as it can permit the evaluation of trace data even if the traces are lost.
Symptoms:
If not planned or incorrectly configured, vSAN trace-level messages may be:
- Taking up a lot of space on ESXi hosts running from a RAM disk
- Written to non persistent storage