Standardising env vars TRACEPARENT
and TRACESTATE
in OTel specification
#156
Labels
enhancement
New feature or request
I was told about this project yesterday and I am very excited by the work you are doing.
Have you considered "upstreaming" your usage of
TRACEPARENT
andTRACESTATE
environment variables to the OpenTelemetry specification? I feel that it would be a valuable addition to the spec. There was an issue opened about a year ago regarding env vars as carriers but it hasn't since progressed: open-telemetry/opentelemetry-specification#740.I feel it would be valuable because there are a few different solutions currently out there and they are generally vendor-specific. E.g.
HONEYCOMB_TRACE
environment variable.BUILDKITE_TRACE_CONTEXT
environment variable with the OpenTracing context.Right now there are very few general-purpose tools that emit distributed tracing data and I expect it's because there is no standard. It could be exceedingly useful to have unit test frameworks emit spans for test suites, have infrastructure-as-code tools (e.g. Terraform, CDK) emit spans for resource creation, have integration tests propagate spans to systems under test, etc. And it feels that this plugin's choice of env vars has the best chance of being generally useful and achieving this goal.
What are your thoughts? I imagine that @v1v and/or @cyrille-leclerc both have more experience in the OTel space than I do personally. I would be happy to attempt to submit an OTEP for this idea, but I imagine that either of you might have a better idea of how to do so successfully.
The text was updated successfully, but these errors were encountered: