-
Notifications
You must be signed in to change notification settings - Fork 91
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
Auto-instrumentation: Incoming and outgoing HTTP requests create separate, uncorrelated traces #1200
Comments
Hello can pls anyone provide update on this I tried multiple ways but still facing same issue @RonFed |
Hi, can you please share the logs from the auto-instrumentation agent? |
@damemi pls find attaced logs
|
@shravanv1 do you have the full logs from the agent from when it starts up? Not just the logs around the spans. I'm looking for a message that would indicate if your host supports context propagation |
@damemi the thing is when I am using this adding @MrAlias also. As this is a bit urgent I am planing to go live with auto instrumentation on prod. PFA start up logs |
@shravanv1 you pointed out the problem correctly. Currently, for in-process context propagation to work the context of the outgoing request must be a descendant of the one from the incoming request. |
Environment Relevant Instrumentation values:
I'm seeing a similar issue as reported here, but the service we're testing on is a simple "empty" service using our conventions. We use this service for testing and doing exploration like this. Our services generally use I added two endpoints to this service, The service runs in a cluster with Istio, which has datadog tracing enabled. The version we run (1.20) doesn't yet support otel natively, however, the datadog support appears to be including the traceparent/tracestate headers from the tracecontext spec. I ran a test without auto-instrumentation first. I added code to manually propagate only the tracecontext headers, and I still saw consistent results in the Then we enabled auto-instrumentation using the otel operator. Whether with or without manually propagating the tracecontext headers, the headers in
Here's the details of the instrumentation:
|
@RonFed can you pls suggest this why I am getting data like any idea? also I am fixed that context propagation. |
@shravanv1 If I understood the image correctly, the context is propagated from Go to Java and from Java to Go (since they all have the same trace ID). However, the |
@ahawtho Do you know if the go context object is being propagated from the |
@RonFed no I doubt somthing wrong here might be some of my span got dropped or it is not being genrated properly. As you can see the attached pic here there is there are one api 'dpt' is being called from go-mmt-svcs in one trace I am getting the two tarce in one I am not getting one tarce. |
Describe the bug
I am using OpenTelemetry auto-instrumentation in a Go application to trace both incoming and outgoing HTTP requests. However, while I can see traces for incoming requests, the outgoing requests are creating entirely new, uncorrelated traces instead of being part of the same trace as the incoming request.
Environment
Language: Go
Go Version: 1.23.1
OpenTelemetry Go Auto-Instrumentation Version: v0.15.0-alpha
OS: Linux (Amazon Linux 2023)
Kernel Version: 6.1.0
Tracing Backend: Jaeger
Code -
inside dealHandlerV2 I am making http call to another API flights-b2c-misc/v2/daily-steal-deals.* by craeting this
but for /v1/thor/rest/flight/home/deals I am getting another trace and for flights-b2c-misc/v2/daily-steal-deals.* I am getting different tarce ideally this sholud be same
The text was updated successfully, but these errors were encountered: