Description
Tracer Version(s)
2.9.0
Ruby Version(s)
ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [x86_64-linux]
Relevent Library and Version(s)
faraday 2.12.2, httpx 1.4.0 (or gh-70 branch)
Bug Report
I got a bug report related to the datadog integration for httpx, which I've narrowed down to the faraday datadog integration (where faraday uses httpx as a backend, and httpx integration is itself turned off). In the report, the reporter shows a screenshot of a request span not propagating to the next service, which also integrates with datadog and has distributed tracing turned on.
While reproducing the issue, as per one of my last messages in the thread, I was able to spot some different behaviour in the faraday datadog integration (compared to the httpx integration) where, when under an active trace, the faraday span appears before the top span (see linked tests).
Something tells me that this is all related, and a bug perhaps in the faraday integration, as the span should have been appended instead, and this lack of ordering is what may cause the distributed tracing not to work in this case.
Any help appreciated.
Reproduction Code
No response
Configuration Block
No response
Error Logs
No response
Operating System
No response
How does Datadog help you?
No response