2.4 KiB
2.4 KiB
Semantic Conventions for MongoDB
Status: Experimental
The Semantic Conventions for MongoDB extend and override the Database Semantic Conventions that describe common database operations attributes in addition to the Semantic Conventions described on this page.
db.system MUST be set to "mongodb".
Attributes
| Attribute | Type | Description | Examples | Requirement Level | Stability |
|---|---|---|---|---|---|
db.collection.name |
string | The MongoDB collection being accessed within the database stated in db.name. [1] |
public.users; customers |
Required |
|
db.operation.name |
string | The name of the command being executed. [2] | findAndModify; getMore; update |
Conditionally Required [3] |
[1]: If the collection name is parsed from the query, it SHOULD match the value provided in the query and may be qualified with the schema and database name.
[2]: See MongoDB database commands.
[3]: If readily available. Otherwise, if the instrumentation library parses db.query.text to capture db.operation.name, then it SHOULD be the first operation name found in the query.
Example
| Key | Value |
|---|---|
| Span name | "products.findAndModify" |
db.system |
"mongodb" |
server.address |
"mongodb0.example.com" |
server.port |
27017 |
network.peer.address |
"192.0.2.14" |
network.peer.port |
27017 |
network.transport |
"tcp" |
db.name |
"shopDb" |
db.statement |
not set |
db.operation |
"findAndModify" |
db.mongodb.collection |
"products" |