You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested to know if there is an existing mechanism that automatically adds this header, or if there is any ongoing development for this feature. If not, I would like to suggest its implementation.
The benefit of this feature would be to pass the trace information to the calling client, even if the client did not originally set up the trace, allowing the client to use the trace ID for troubleshooting purposes.
The text was updated successfully, but these errors were encountered:
I believe this needs to be first defined in the OTel specification, before implementations start adding it. There's already an issue open in the OTel spec repo: open-telemetry/opentelemetry-specification#1355
Title: Add Support for
traceresponse
Header in OpenTelemetry TracingDescription:
I propose adding
traceresponse
headers, as defined by the Trace Response Header Specification, when OpenTelemetry tracing is enabled.I didn't find any references to this header in the documentation: Tracing and OpenTelemetry tracer (proto).
I'm interested to know if there is an existing mechanism that automatically adds this header, or if there is any ongoing development for this feature. If not, I would like to suggest its implementation.
The benefit of this feature would be to pass the trace information to the calling client, even if the client did not originally set up the trace, allowing the client to use the trace ID for troubleshooting purposes.
The text was updated successfully, but these errors were encountered: