Orchestrated way to define a logger for tracing when instrumented with Orchestrion

[gabizou]

Package Name

No response

Package Version(s)

No response

Describe the feature you'd like

Currently, when an application is orchestrated with Orchestrion, there's no feasible way to define the logger in use (as I'd prefer to have logs outputted in json format from application start) for the initial startup message logging.

A suggested workaround from @RomainMuller which is less than ideal

The default instrumentation does not specify any logger option at tracer start and there is currently no way to have it specify one. An option is to stop orchestrion from auto-starting the tracer and doing this yourself...
You might want to file an issue on the DataDog/dd-trace-go repository to request a way to specify tracer.UserLogger options for the tracer start orchestrion instrumentation... so this gets on the radar of the relevant folks.

Per the suggestion, I could imagine a defined commented function to signal orchestration as "hey, here's a zero arg logger supplier function" so that tracer.UseLogger can be orchestrated in startup.

Is your feature request related to a problem?

No response

Describe alternatives you've considered

No response

Additional context

No response