-
Notifications
You must be signed in to change notification settings - Fork 97
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
TraceID does not match with TraceID inside the trace header #845
Comments
Indeed trace context propagation is supported as exposed.
|
Hi @jpicara, There are some limitations in what Beyla can do related to trace ID propagation, some of which will be resolved in the next couple of releases, but let me first ask couple of questions and explain better.
Please let me know if you have more questions, happy to help! |
Hey,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!,
I would like to report the following issue we are suffering. We have deployed Beyla, Agent and Tempo in our testing environment and from what I have observed, we are not able to correlate the traceID set into the trace headers with the traceID got from Beyla itself. As an example.
Doing a simple curl to specific endpoint I can get the headers
However the same trace in Beyla is marked with some random? traceID 147c58703a0a4df9e052bf86d5026785.
Is there any way to patch the traceID with our X-Trace-Token or X-B3-TraceId? In addition to that, this traceID and SpanID set by beyla is somehow random?
Thanks in advance!
The text was updated successfully, but these errors were encountered: