-
Notifications
You must be signed in to change notification settings - Fork 171
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
Semantic Conventions for MongoDB #709
Comments
One interesting attribute is duration_micros: the duration the query took to actually execute. I was originally thinking this may not be a good attribute to add, but there are edge cases that are worth being able to detect like significant time spent in the deserialization of the payload, rather than in the query itself. |
That might even make sense as a generic span semantic convention like
Or we might want an event semantic convention for that. |
I think a generic semantic convention makes a lot of sense, and maybe we can add examples in each semantic convention on the use case (e.g. db query time for the db calls). I'll send a PR to continue the conversation? |
I believe this can be closed, as this is very old and we have both generic database semantic conventions and mongodb semantic conventions now |
* Add OTEL_SERVICE_NAME environment variable Closes open-telemetry#709
What are you trying to achieve?
Reach a conclusion on what fields to expose for MongoDB, on top of the existing ones.
Standardizing on the right keys would be great, but I don't have a specific proposal in mind. Just raising the thread in case anyone has a perspective.
Additional context.
Here's a couple examples of Mongo instrumentation:
The text was updated successfully, but these errors were encountered: