Log field for the VU's ID

[codebien]

Feature Description

In some cases, like this forum question, can be helpful to know which specific VU is executing the code or just know that the logs are generated by one of the VUID == 0 (options resolution, babel transpiler, setup, teardown, handle summary).

This was originally proposed during the Init Context's implementation of the console.log.

Suggested Solution (optional)

And if we can fix the configuration challenges you describe (sob), have proper loggers per-VU, and actually implement #889 and attach (via log.WithFields()) the VU ID to each log message, any user confusion from multiple identical messages will likely disappear.

This suggested solution from the original issue is still a valid option.

Already existing or connected issues / PRs (optional)

#951
#2344 - We want to deprecate common.Bind that is how the console.log is defined. A refactor on that side will be for sure beneficial also for the current issue.

[mstoykov]

I am not so certain this will help so much as a bunch of those will be VU=0

And to be honest this is a thing a user can add to the log every time if they so desire along with any other information.

Having it by default will likely just make everything more noisy than anything 🤷

[codebien]

Considering the lack of reactions it sounds like a not very requested feature.