-
Notifications
You must be signed in to change notification settings - Fork 375
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
Type error when enabling full mysql2 comment propagation #2852
Comments
I am seeing the same issue with postgres as well: Callstack:
I upgraded some gems to try to work around it:
Environment: WorkaroundIf I set c.tracing.instrument(:pg, comment_propogation: 'full') if c.tracing.enabled |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour
We have added the following line to our Datadog configuration in our Rails app, per the docs.
Now, when our app issues any database statement, we see a type error:
I'm not completely sure, but I think this might be caused by a missing span ID (inserting a debugger at the line above, I can see that the
parent_id
argument tobuild_traceparent_string
isnil
).Expected behaviour
We were expecting to be able to enable comment propagation without an error, and have DBM traces linked to APM, and vice versa.
Steps to reproduce
We are using
ddtrace
in a Rails app (6.1.7). Here is our full Datadog configuration:Here is the full stacktrace:
Environment
Datadog.configure ...
): See aboveThe text was updated successfully, but these errors were encountered: