-
Notifications
You must be signed in to change notification settings - Fork 599
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
Make sure database instrumentations follow semantic conventions #159
Comments
Hi @lzchen, I would like to work on this. I have read the specification and gone through some database instrumentations. Here are the thins I noticed.
|
Hi @lzchen , I tried to address this here. @toumorokoshi left some comments I think there's still some reconciliation that needs to happen on the specification and the fields emitted, especially on the MongoDB side. Some db specific call level attributes are added which are not mentioned in spec. What are your thoughts on this? |
Hey @lonewolf3739! Sorry about the hassle, but would you mind sending your PR again? I think the libraries moved to this repo while this PR was still in discussion. Regarding:
Here's a spec ticket to start a discussion. I think some of this may be follow-up work as well, so the PR as-is would be great to merge in. |
@toumorokoshi I don't mind opening PR here again. I just wanted to see if others can chime in and share their opinions. |
@lonewolf3739
The extra attributes not defined in the specs can be left until the specs are finalized. |
This issue was marked stale due to lack of activity. It will be closed in 30 days. |
Are there any more remaining? |
@awssandra We haven't made any changes since last time. I think there would be some gaps between the specification and current implementation. |
I will create a new issue with the same title and epic containing all the db instrumentations. |
From specs.
The text was updated successfully, but these errors were encountered: