Otel B3 propagator is not matching traces between consumer record header and http request header #5127
Unanswered
mounikaVeeha
asked this question in
Q&A
Replies: 0 comments 1 reply
-
Sounds like this is an auto-instrumentation question. I'll move it over to the appropriate place. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a requirement to match the traces when a call goes from consumer to rest API.Here we are using b3 propogators . The traces in the record header are not matching with the traces in the rest API (HTTP Request).How to match the trace present in record header to trace in the request header as both headers have different traces (x-b3-traceId).
Also can we change/modify the agent generated Trace id (traceId generated using auto instrumentation ) with custom traceId .
Beta Was this translation helpful? Give feedback.
All reactions