Spans are orphaned when using datadog backend #7
Unanswered
clarkenciel
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! First, thanks for providing these tracing facades so we don't have to monkeypatch
async
.I currently use datadog for APM and have observed that APM spans get orphaned in code running inside of tasks spawned by
async
. Going by this issue it seems to be because datadog doesn't support fiber-based context. I've seen the issues you've created and found my way to the traces family of gem.When I try to use
Traces
with the datadog backend I still see orphaned spans so I wonder if I'm using it incorrectly. For example, I've got the following test script which I run withTRACES_BACKEND=traces/backend/datadog ruby async.rb
:And this produces traces like so:
Note that while all the spans make their way into APM, the child traces are detached from their parents. My hope was that these libraries would manage these links automatically.
Beta Was this translation helpful? Give feedback.
All reactions