Semantic Conventions for Cassandra

Status: Experimental

The Semantic Conventions for Cassandra 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 "cassandra".

Attributes

AttributeTypeDescriptionExamplesRequirement LevelStability
db.collection.namestringThe name of the Cassandra table that the operation is acting upon. [1]public.users; customersConditionally Required [2]Experimental
db.namespacestringThe Cassandra keyspace name. [3]mykeyspaceConditionally Required If available.Experimental
db.operation.namestringThe name of the operation or command being executed. [4]findAndModify; HMSET; SELECTConditionally Required [5]Experimental
error.typestringDescribes a class of error the operation ended with. [6]timeout; java.net.UnknownHostException; server_certificate_invalid; 500Conditionally Required If and only if the operation failed.Stable
server.portintServer port number. [7]80; 8080; 443Conditionally Required [8]Stable
db.cassandra.consistency_levelstringThe consistency level of the query. Based on consistency values from CQL.all; each_quorum; quorumRecommendedExperimental
db.cassandra.coordinator.dcstringThe data center of the coordinating node for a query.us-west-2RecommendedExperimental
db.cassandra.coordinator.idstringThe ID of the coordinating node for a query.be13faa2-8574-4d71-926d-27f16cf8a7afRecommendedExperimental
db.cassandra.idempotencebooleanWhether or not the query is idempotent.RecommendedExperimental
db.cassandra.page_sizeintThe fetch size used for paging, i.e. how many rows will be returned at once.5000RecommendedExperimental
db.cassandra.speculative_execution_countintThe number of times a query was speculatively executed. Not set or 0 if the query was not executed speculatively.0; 2RecommendedExperimental
db.query.textstringThe database query being executed.SELECT * FROM wuser_table where username = ?; SET mykey "WuValue"Recommended [9]Experimental
network.peer.addressstringPeer address of the database node where the operation was performed. [10]10.1.2.80; /tmp/my.sockRecommendedStable
network.peer.portintPeer port number of the network connection.65123Recommended if and only if network.peer.address is set.Stable
server.addressstringName of the database host. [11]example.com; 10.1.2.80; /tmp/my.sockRecommendedStable
db.query.parameter.<key>stringThe query parameters used in db.query.text, with <key> being the parameter name, and the attribute value being the parameter value. [12]someval; 55Opt-InExperimental

[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]: For commands that switch the keyspace, this SHOULD be set to the target keyspace (even if the command fails).

[4]: It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.

[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]: If a database operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.

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

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

db.cassandra.consistency_level 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.

ValueDescriptionStability
allallExperimental
each_quorumeach_quorumExperimental
quorumquorumExperimental
local_quorumlocal_quorumExperimental
oneoneExperimental
twotwoExperimental
threethreeExperimental
local_onelocal_oneExperimental
anyanyExperimental
serialserialExperimental
local_seriallocal_serialExperimental

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.

ValueDescriptionStability
_OTHERA fallback error value to be used when the instrumentation doesn’t define a custom value.Stable