Using pino-opentelemetry-transport without OpenTelemetry Pino instrumentations

[segevfiner]

Currently pino-opentelemetry-transport reads the tracing attributes added by OpenTelemetry in the worker, relying on the Pino instrumentation of OpenTelemtry to be configured without it's builtin log sending enabled to add them. It would be much nicer to be able to use it without requiring that though. But something is currently missing from the transport API, which also effects other transports like for Sentry for example. There is no option for the transport to run code in the main thread to collect additional information that is only available in the main thread before it gets sent to the worker. This makes such transports be impractical for actual use and will require using a normal stream instead for those if you don't want to lose important information.

[Vunovati]

Hello @segevfiner, can you write a small code snippet explaining a use-case where using transport is impractical? In general using worker-thread pino v7 transport was the goal for this transport from the start.