-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for traceresponse
Header in OpenTelemetry Tracing
#36666
Comments
add @AlexanderEllis @yanavlasov based on CODEOWNER Also, add @joaopgrassi and @wbpcode as you worked on opentelemetry tracer in the past (e.g., #29207) |
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 |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Remove stale |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Remove stale |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Remove stale |
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: