Semantic Conventions for SQL Databases
Status: Experimental
The SQL databases Semantic Conventions extend and override the Database Semantic Conventions that describe common database operations attributes in addition to the Semantic Conventions described on this page.
Call-level attributes
| Attribute | Type | Description | Examples | Requirement Level |
|---|---|---|---|---|
db.sql.table | string | The name of the primary table that the operation is acting upon, including the database name (if applicable). [1] | public.users; customers | Recommended |
[1]: It is not recommended to attempt any client-side parsing of db.statement just to get this property, but it should be set if it is provided by the library being instrumented. If the operation is acting upon an anonymous table, or more than one table, this value MUST NOT be set.
Example
This is an example of attributes for a MySQL database span:
| Key | Value |
|---|---|
| Span name | "SELECT ShopDb.orders" |
db.system | "mysql" |
db.connection_string | "Server=shopdb.example.com;Database=ShopDb;Uid=billing_user;TableCache=true;UseCompression=True;MinimumPoolSize=10;MaximumPoolSize=50;" |
db.user | "billing_user" |
server.address | "shopdb.example.com" |
server.port | 3306 |
network.peer.address | "192.0.2.12" |
network.peer.port | 3306 |
network.transport | "tcp" |
db.name | "ShopDb" |
db.statement | "SELECT * FROM orders WHERE order_id = 'o4711'" |
db.operation | "SELECT" |
db.sql.table | "orders" |