Is your feature request related to a problem? Please describe.
We have a trigger.dev task that clones a repo and spawns a child process to run a script there. Obviously no traces reach the global trigger.dev tracer from separate node process. What would work is if we could register NodeTracerProvider with OTLPTraceExporter set to OTEL_EXPORTER_OTLP_ENDPOINT/OTEL_EXPORTER_OTLP_HEADERS of trigger.dev task (parent process).
OTEL_EXPORTER_OTLP_ENDPOINT is there, but OTEL_EXPORTER_OTLP_HEADERS is not exposed, so no way to direct spans to the right trigger run's trace provider
Describe the solution you'd like to see
Export something like runTracerSdk or maybe expose OTEL_EXPORTER_OTLP_HEADERS as variable on run ctx
Describe alternate solutions
No idea, I currently send child spans through IPC, but it sucks
Additional information
No response
Is your feature request related to a problem? Please describe.
We have a trigger.dev task that clones a repo and spawns a child process to run a script there. Obviously no traces reach the global trigger.dev tracer from separate node process. What would work is if we could register
NodeTracerProviderwithOTLPTraceExporterset toOTEL_EXPORTER_OTLP_ENDPOINT/OTEL_EXPORTER_OTLP_HEADERSof trigger.dev task (parent process).OTEL_EXPORTER_OTLP_ENDPOINTis there, butOTEL_EXPORTER_OTLP_HEADERSis not exposed, so no way to direct spans to the right trigger run's trace providerDescribe the solution you'd like to see
Export something like runTracerSdk or maybe expose OTEL_EXPORTER_OTLP_HEADERS as variable on run ctx
Describe alternate solutions
No idea, I currently send child spans through IPC, but it sucks
Additional information
No response