-
Notifications
You must be signed in to change notification settings - Fork 3
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
Datadog instrumentation breaks pymongo with ddtrace<2.7.9 #580
Comments
@timmc-edx is this ticket blocked until the DD side investigation has returned some findings? |
Yes, and we can leave it either in No Status or in Blocked. |
timmc-edx
changed the title
Tracking: Datadog instrumentation breaks pymongo
Datadog instrumentation breaks pymongo with ddtrace<2.7.9
Apr 23, 2024
Ticket scope has been updated, so this ticket is now Ready to be picked up. |
timmc-edx
added a commit
to edx/configuration
that referenced
this issue
Aug 7, 2024
ddtrace 2.7.9 and 2.8.2 were released with a fix for this issue, and we've since upgraded past these. See edx/edx-arch-experiments#580
3 tasks
timmc-edx
added a commit
to edx/configuration
that referenced
this issue
Aug 8, 2024
ddtrace 2.7.9 and 2.8.2 were released with a fix for this issue, and we've since upgraded past these. See edx/edx-arch-experiments#580
Completed in edx/configuration#59 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A/C:
Important note: Follow roll-out of proving out on Stage, then moving to Edge, then moving to Prod.
When we tried instrumenting edxapp with Datadog APM (via
ddtrace-run
) it caused some pymongo calls to break. This was with ddtrace-run 2.7.3 and pymongo 3.13.0. UsingDD_TRACE_PYMONGO_ENABLED=false
prevents the errors.Versions 2.7.9 and 2.8.2 contain a fix; I've verified the fix in 2.7.9 in devstack.
Stack trace:
Private support ticket: https://help.datadoghq.com/hc/en-us/requests/1600528
The text was updated successfully, but these errors were encountered: