Symptoms:
Large number of logging events are generated in the vsanmgmt.log from vsand process when events include structured data.
For example, a single "message" generates 15 log entries with payload data chunked across them. This generates a large amount of events that required extra processing by remote log hosts like Log Insight. Because the events are stored separately, the payload data loses it's context.vsanmgmt.log:2025-04-08T23:16:26.095Z In(14) vsand[2101688]: [opID=#######-#### VsanPerformanceManagerImpl::executeQueryNodeInfo] QueryNodeInformation result: (vim.cluster.VsanPerfNodeInformation) {vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: version = '8.0.203',vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: isCmmdsMaster = true,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: isStatsMaster = true,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: vsanMasterUuid = '64cc12c9-b8a4-a747-####-############',vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: vsanNodeUuid = '64cc12c9-b8a4-a747-####-############',vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: masterInfo = (vim.cluster.VsanPerfMasterInformation) {vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: secSinceLastStatsWrite = 167,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: secSinceLastStatsCollect = 168,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: statsIntervalSec = 300,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: statsDirectoryPercentFree = 97,vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: verboseMode = falsevsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: },vsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: diagnosticMode = falsevsanmgmt.log:2025-04-08T23:16:26.095Z In(14)[+] vsand[2101688]: }
VMware vSAN 7.x
VMware vSAN 8.x
Broadcom Engineering identified the logs formatting issue and they are actively working on a fix.
There is currently no resolution for this issue. Broadcom Engineering is working on a fix.
Update ESXi Hosts to the new version with the fix included once released.