-
Notifications
You must be signed in to change notification settings - Fork 0
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
[SERF-2055] Replacing custom database tracing with dd-trace-go/contrib library #106
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I did a quick pass and left 2 comments. 💬
c9c081c
to
0ac4264
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM 🚀
145a375
to
ac1cad5
Compare
ac1cad5
to
0cb4dd5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Description
By now, we've been using our own trace since we were using an outdated
gorm
version. Now that we are to the (almost) latestgorm
version, we can start using community supported tracing.A new version will be released after merging this PR.
Testing considerations
Code is tested on
document-search
staging, having spans with the new library.Checklist
development
and/orstaging
README.md
as necessaryRelated links