is vsantrace logs are vsan component?

[b4nganto]

hello,

we run vsan 6.2 in our environtment, and we setup log insight with vsan for log monitoring. In log insight, i watch that "vsantraceurgent" always appear on vsan object component absent dashboard. what i want to know.. is vsantrace logs are part of vsan component? why that logs always appear on vsan object component dashboard?

i would appreciate any comments.

regards,

hadi ismanto

[SureshKumarMuth]

Hi,

Yes, vsantrace log is a component of vsan to record vsan related events. The error messages what you've updated shows that one of the component is in absent state, please check why the components state went in absent.

You may raise a case with Vmware to check the object state and to remove that particular component if it is not actually needed or take corrective actions to stop these error messages

[TheBobkin]

Hello Hadi,

vsantraces are extremely-detailed verbose logging that are typically written to a RAMdisk and a very small proportion saved to /locker (as they get rotated typically within minutes).

This logging is only really useful for troubleshooting issues when being intentionally reproduced or occurring presently.

My understanding of it is that vsantraces has two log outputs:

vsantraces - verbose output of cluster and object-level activity.

vsantracesUrgent - as the name suggests, verbose logging that is related to a problem occurring with cluster or objects/components, like in this case where components have changed state from 'active' to 'absent':

(" 'oldCompState: 'active, 'newCompState': 'absent' " e.g: old component state was 'active' component now marked as 'absent' , this type of event likely coincides with some other issue in the cluster such as a host losing connectivity to the rest of the cluster, a controller reset, a failed disk/disk-group, whether this event/status was transient or not can be determined by when/if you see  the opposite logging for the same UUID e.g: " 'oldCompState: 'absent', 'newCompState': 'active' " ).

Are you using Log Insight configured for syslog?

If so then the following will make sense as to why vsantracesUrgent is being seen here as this is the default:

https://kb.vmware.com/kb/2145556

Please mark this post as helpful and/or answer if you deem it to be either and leave a comment if you need more info :smileygrin:

Bob

[b4nganto]

hi bob,

thanks for your good comment. :smileyhappy:

regards,