Skip to content

Latest commit

 

History

History
62 lines (42 loc) · 5.73 KB

mssql.md

File metadata and controls

62 lines (42 loc) · 5.73 KB

Semantic Conventions for MSSQL

Status: Experimental

The Semantic Conventions for the Microsoft SQL Server 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 "mssql".

Attributes

Attribute Type Description Examples Requirement Level Stability
db.collection.name string The name of the SQL table that the operation is acting upon. [1] users; dbo.products Conditionally Required [2] Experimental
db.namespace string The name of the database, fully qualified within the server address and port. [3] instance1.products; customers Conditionally Required If available. Experimental
db.operation.name string The name of the operation or command being executed. [4] SELECT; INSERT; UPDATE; DELETE; CREATE; mystoredproc Conditionally Required [5] Experimental
error.type string Describes a class of error the operation ended with. [6] timeout; java.net.UnknownHostException; server_certificate_invalid; 500 Conditionally Required If and only if the operation failed. Stable
server.port int Server port number. [7] 80; 8080; 443 Conditionally Required [8] Stable
db.query.text string The database query being executed. SELECT * FROM wuser_table where username = ?; SET mykey "WuValue" Recommended [9] Experimental
server.address string Name of the database host. [10] example.com; 10.1.2.80; /tmp/my.sock Recommended Stable
db.query.parameter.<key> string The query parameters used in db.query.text, with <key> being the parameter name, and the attribute value being the parameter value. [11] someval; 55 Opt-In Experimental

[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. It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.

[2]: If readily available. Otherwise, if the instrumentation library parses db.query.text to capture db.collection.name, then it SHOULD be the first collection name found in the query.

[3]: When connecting to a default instance, db.namespace SHOULD be set to the name of the database. When connecting to a named instance, db.namespace SHOULD be set to the combination of instance and database name following the {instance_name}.{database_name} pattern. For commands that switch the database, this SHOULD be set to the target database (even if the command fails).

[4]: This SHOULD be the SQL command such as SELECT, INSERT, UPDATE, CREATE, DROP. In the case of EXEC, this SHOULD be the stored procedure name that is being executed.

[5]: 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.

[6]: The error.type SHOULD match the error code returned by the database or the client library, the canonical name of exception that occurred, or another low-cardinality error identifier. Instrumentations SHOULD document the list of errors they report.

[7]: When observed from the client side, and when communicating through an intermediary, server.port SHOULD represent the server port behind any intermediaries, for example proxies, if it's available.

[8]: If using a port other than the default port for this DBMS and if server.address is set.

[9]: SHOULD be collected by default only if there is sanitization that excludes sensitive information.

[10]: When observed from the client side, and when communicating through an intermediary, server.address SHOULD represent the server address behind any intermediaries, for example proxies, if it's available.

[11]: Query parameters should only be captured when db.query.text is parameterized with placeholders. If a parameter has no name and instead is referenced only by index, then <key> SHOULD be the 0-based index.

error.type has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

Value Description Stability
_OTHER A fallback error value to be used when the instrumentation doesn't define a custom value. Stable