Semantic Conventions for MongoDB

[toumorokoshi]

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 Python PyMongo instrumentation stores the operation and request id.
• The Java instrumentation doesn't set a lot of attributes, But it may be possible extract more.

[toumorokoshi]

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.

[Oberon00]

One interesting attribute is duration_micros: the duration the query took to actually execute.

That might even make sense as a generic span semantic convention like

span.child_time: Use this attribute when this span represents a call into (potentially) uninstrumented code that reports back how long it took to perform the requested operation. Set it to the operation's reported duration in nanoseconds.

Or we might want an event semantic convention for that.

[toumorokoshi]

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?

[trask]

I believe this can be closed, as this is very old and we have both generic database semantic conventions and mongodb semantic conventions now