Semantic Conventions for CouchDB

Status: Experimental

The Semantic Conventions for CouchDB 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 "couchdb".

Attributes

Attribute	Type	Description	Examples	Requirement Level	Stability
db.namespace	string	The name of the database, fully qualified within the server address and port. [1]	customers; test.users	Conditionally Required If available.
db.operation.name	string	The HTTP method + the target REST route. [2]	GET /{db}/{docid}	Conditionally Required [3]
error.type	string	Describes a class of error the operation ended with. [4]	timeout; java.net.UnknownHostException; server_certificate_invalid; 500	Conditionally Required If and only if the operation failed.
server.port	int	Server port number. [5]	80; 8080; 443	Conditionally Required [6]
server.address	string	Name of the database host. [7]	example.com; 10.1.2.80; /tmp/my.sock	Recommended

[1]:

[2]: In CouchDB, db.operation.name should be set to the HTTP method + the target REST route according to the API reference documentation. For example, when retrieving a document, db.operation.name would be set to (literally, i.e., without replacing the placeholders with concrete values): GET /{db}/{docid}.

[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.

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

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

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

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

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.