Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Expose jaeger/opentracing trace id in response so clients can log it #9480

Closed
bwindels opened this issue Feb 24, 2021 · 0 comments · Fixed by #10199
Closed

Expose jaeger/opentracing trace id in response so clients can log it #9480

bwindels opened this issue Feb 24, 2021 · 0 comments · Fixed by #10199
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@bwindels
Copy link
Contributor

This should help debugging across the client/server boundary.
@bwindels bwindels mentioned this issue Feb 24, 2021
Closed
@richvdh richvdh mentioned this issue Jun 17, 2021
Merged
@MadLittleMods MadLittleMods added the T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. label Jun 17, 2021
richvdh added a commit that referenced this issue Jun 18, 2021
@richvdh
Expose opentracing trace id in response headers (#10199)
91fa9cc 
Fixes: #9480
This was referenced Aug 23, 2021
Open
Open
Open
Open
@bwindels bwindels mentioned this issue Jan 31, 2023
Closed
@H-Shay H-Shay mentioned this issue Feb 7, 2023
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Expose opentracing trace id in response headers matrix-org/synapse
2 participants
@bwindels @MadLittleMods