Class DbIncubatingAttributes
java.lang.Object
io.opentelemetry.semconv.incubating.DbIncubatingAttributes
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic final classValues forDB_CASSANDRA_CONSISTENCY_LEVEL.static final classDeprecated.Deprecated, use `db.client.connection.state` instead.static final classValues forDB_CLIENT_CONNECTION_STATE.static final classValues forDB_COSMOSDB_CONNECTION_MODE.static final classValues forDB_COSMOSDB_OPERATION_TYPE.static final classValues forDB_SYSTEM. -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final io.opentelemetry.api.common.AttributeKey<String>The consistency level of the query.static final io.opentelemetry.api.common.AttributeKey<String>The data center of the coordinating node for a query.static final io.opentelemetry.api.common.AttributeKey<String>The ID of the coordinating node for a query.static final io.opentelemetry.api.common.AttributeKey<Boolean>Whether or not the query is idempotent.static final io.opentelemetry.api.common.AttributeKey<Long>The fetch size used for paging, i.e. how many rows will be returned at once.static final io.opentelemetry.api.common.AttributeKey<Long>The number of times a query was speculatively executed.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.collection.name` instead.static final io.opentelemetry.api.common.AttributeKey<String>The name of the connection pool; unique within the instrumented application.static final io.opentelemetry.api.common.AttributeKey<String>The state of a connection in the poolstatic final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.client.connection.pool.name` instead.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.client.connection.state` instead.static final io.opentelemetry.api.common.AttributeKey<String>The name of a collection (table, container) within the database.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `server.address`, `server.port` attributes instead.static final io.opentelemetry.api.common.AttributeKey<String>Unique Cosmos client instance id.static final io.opentelemetry.api.common.AttributeKey<String>Cosmos client connection mode.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.collection.name` instead.static final io.opentelemetry.api.common.AttributeKey<String>CosmosDB Operation Type.static final io.opentelemetry.api.common.AttributeKey<Double>RU consumed for that operationstatic final io.opentelemetry.api.common.AttributeKey<Long>Request payload size in bytesstatic final io.opentelemetry.api.common.AttributeKey<Long>Cosmos DB status code.static final io.opentelemetry.api.common.AttributeKey<Long>Cosmos DB sub status code.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.namespace` instead.static final io.opentelemetry.api.common.AttributeKey<String>Represents the human-readable identifier of the node/instance to which a request was routed.static final io.opentelemetry.semconv.AttributeKeyTemplate<String>A dynamic value in the url path.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, no general replacement at this time.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Removed, no replacement at this time.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.collection.name` instead.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, SQL Server instance is now populated as a part of `db.namespace` attribute.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.namespace` instead.static final io.opentelemetry.api.common.AttributeKey<String>The name of the database, fully qualified within the server address and port.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.operation.name` instead.static final io.opentelemetry.api.common.AttributeKey<Long>The number of queries included in a batch operation.static final io.opentelemetry.api.common.AttributeKey<String>The name of the operation or command being executed.static final io.opentelemetry.semconv.AttributeKeyTemplate<String>A query parameter used indb.query.text, with<key>being the parameter name, and the attribute value being a string representation of the parameter value.static final io.opentelemetry.api.common.AttributeKey<String>The database query being executed.static final io.opentelemetry.api.common.AttributeKey<Long>Deprecated.Deprecated, use `db.namespace` instead.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, use `db.collection.name` instead.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.The database statement being executed.static final io.opentelemetry.api.common.AttributeKey<String>The database management system (DBMS) product as identified by the client instrumentation.static final io.opentelemetry.api.common.AttributeKey<String>Deprecated.Deprecated, no replacement at this time. -
Method Summary
-
Field Details
-
DB_CASSANDRA_CONSISTENCY_LEVEL
The consistency level of the query. Based on consistency values from CQL. -
DB_CASSANDRA_COORDINATOR_DC
The data center of the coordinating node for a query. -
DB_CASSANDRA_COORDINATOR_ID
The ID of the coordinating node for a query. -
DB_CASSANDRA_IDEMPOTENCE
Whether or not the query is idempotent. -
DB_CASSANDRA_PAGE_SIZE
The fetch size used for paging, i.e. how many rows will be returned at once. -
DB_CASSANDRA_SPECULATIVE_EXECUTION_COUNT
public static final io.opentelemetry.api.common.AttributeKey<Long> DB_CASSANDRA_SPECULATIVE_EXECUTION_COUNTThe number of times a query was speculatively executed. Not set or0if the query was not executed speculatively. -
DB_CASSANDRA_TABLE
Deprecated.Deprecated, use `db.collection.name` instead.Deprecated, usedb.collection.nameinstead. -
DB_CLIENT_CONNECTION_POOL_NAME
The name of the connection pool; unique within the instrumented application. In case the connection pool implementation doesn't provide a name, instrumentation SHOULD use a combination of parameters that would make the name unique, for example, combining attributesserver.address,server.port, anddb.namespace, formatted asserver.address:server.port/db.namespace. Instrumentations that generate connection pool name following different patterns SHOULD document it. -
DB_CLIENT_CONNECTION_STATE
The state of a connection in the pool -
DB_CLIENT_CONNECTIONS_POOL_NAME
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_CLIENT_CONNECTIONS_POOL_NAMEDeprecated.Deprecated, use `db.client.connection.pool.name` instead.Deprecated, usedb.client.connection.pool.nameinstead. -
DB_CLIENT_CONNECTIONS_STATE
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_CLIENT_CONNECTIONS_STATEDeprecated.Deprecated, use `db.client.connection.state` instead.Deprecated, usedb.client.connection.stateinstead. -
DB_COLLECTION_NAME
The name of a collection (table, container) within the database.Notes:
- It is RECOMMENDED to capture the value as provided by the application without attempting
to do any case normalization. If the collection name is parsed from the query text, it
SHOULD be the first collection name found in the query and it SHOULD match the value
provided in the query text including any schema and database name prefix. For batch
operations, if the individual operations are known to have the same collection name then
that collection name SHOULD be used, otherwise
db.collection.nameSHOULD NOT be captured.
- It is RECOMMENDED to capture the value as provided by the application without attempting
to do any case normalization. If the collection name is parsed from the query text, it
SHOULD be the first collection name found in the query and it SHOULD match the value
provided in the query text including any schema and database name prefix. For batch
operations, if the individual operations are known to have the same collection name then
that collection name SHOULD be used, otherwise
-
DB_CONNECTION_STRING
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_CONNECTION_STRINGDeprecated.Deprecated, use `server.address`, `server.port` attributes instead.Deprecated, useserver.address,server.portattributes instead. -
DB_COSMOSDB_CLIENT_ID
Unique Cosmos client instance id. -
DB_COSMOSDB_CONNECTION_MODE
Cosmos client connection mode. -
DB_COSMOSDB_CONTAINER
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_COSMOSDB_CONTAINERDeprecated.Deprecated, use `db.collection.name` instead.Deprecated, usedb.collection.nameinstead. -
DB_COSMOSDB_OPERATION_TYPE
CosmosDB Operation Type. -
DB_COSMOSDB_REQUEST_CHARGE
RU consumed for that operation -
DB_COSMOSDB_REQUEST_CONTENT_LENGTH
public static final io.opentelemetry.api.common.AttributeKey<Long> DB_COSMOSDB_REQUEST_CONTENT_LENGTHRequest payload size in bytes -
DB_COSMOSDB_STATUS_CODE
Cosmos DB status code. -
DB_COSMOSDB_SUB_STATUS_CODE
Cosmos DB sub status code. -
DB_ELASTICSEARCH_CLUSTER_NAME
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_ELASTICSEARCH_CLUSTER_NAMEDeprecated.Deprecated, use `db.namespace` instead.Deprecated, usedb.namespaceinstead. -
DB_ELASTICSEARCH_NODE_NAME
Represents the human-readable identifier of the node/instance to which a request was routed. -
DB_ELASTICSEARCH_PATH_PARTS
public static final io.opentelemetry.semconv.AttributeKeyTemplate<String> DB_ELASTICSEARCH_PATH_PARTSA dynamic value in the url path.Notes:
- Many Elasticsearch url paths allow dynamic values. These SHOULD be recorded in span
attributes in the format
db.elasticsearch.path_parts.<key>, where<key>is the url path part name. The implementation SHOULD reference the elasticsearch schema in order to map the path part values to their names.
- Many Elasticsearch url paths allow dynamic values. These SHOULD be recorded in span
attributes in the format
-
DB_INSTANCE_ID
Deprecated.Deprecated, no general replacement at this time. For Elasticsearch, use `db.elasticsearch.node.name` instead.Deprecated, no general replacement at this time. For Elasticsearch, usedb.elasticsearch.node.nameinstead. -
DB_JDBC_DRIVER_CLASSNAME
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_JDBC_DRIVER_CLASSNAMEDeprecated.Removed, no replacement at this time.Removed, no replacement at this time. -
DB_MONGODB_COLLECTION
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_MONGODB_COLLECTIONDeprecated.Deprecated, use `db.collection.name` instead.Deprecated, usedb.collection.nameinstead. -
DB_MSSQL_INSTANCE_NAME
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<String> DB_MSSQL_INSTANCE_NAMEDeprecated.Deprecated, SQL Server instance is now populated as a part of `db.namespace` attribute.Deprecated, SQL Server instance is now populated as a part ofdb.namespaceattribute. -
DB_NAME
Deprecated.Deprecated, use `db.namespace` instead.Deprecated, usedb.namespaceinstead. -
DB_NAMESPACE
The name of the database, fully qualified within the server address and port.Notes:
- If a database system has multiple namespace components, they SHOULD be concatenated
(potentially using database system specific conventions) from most general to most
specific namespace component, and more specific namespaces SHOULD NOT be captured without
the more general namespaces, to ensure that "startswith" queries for the more
general namespaces will be valid. Semantic conventions for individual database systems
SHOULD document what
db.namespacemeans in the context of that system. It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
- If a database system has multiple namespace components, they SHOULD be concatenated
(potentially using database system specific conventions) from most general to most
specific namespace component, and more specific namespaces SHOULD NOT be captured without
the more general namespaces, to ensure that "startswith" queries for the more
general namespaces will be valid. Semantic conventions for individual database systems
SHOULD document what
-
DB_OPERATION
Deprecated.Deprecated, use `db.operation.name` instead.Deprecated, usedb.operation.nameinstead. -
DB_OPERATION_BATCH_SIZE
The number of queries included in a batch operation.Notes:
- Operations are only considered batches when they contain two or more operations, and so
db.operation.batch.sizeSHOULD never be1.
- Operations are only considered batches when they contain two or more operations, and so
-
DB_OPERATION_NAME
The name of the operation or command being executed.Notes:
- It is RECOMMENDED to capture the value as provided by the application without attempting
to do any case normalization. If the operation name is parsed from the query text, it
SHOULD be the first operation name found in the query. For batch operations, if the
individual operations are known to have the same operation name then that operation name
SHOULD be used prepended by
BATCH, otherwisedb.operation.nameSHOULD beBATCHor some other database system specific term if more applicable.
- It is RECOMMENDED to capture the value as provided by the application without attempting
to do any case normalization. If the operation name is parsed from the query text, it
SHOULD be the first operation name found in the query. For batch operations, if the
individual operations are known to have the same operation name then that operation name
SHOULD be used prepended by
-
DB_QUERY_PARAMETER
A query parameter used indb.query.text, with<key>being the parameter name, and the attribute value being a string representation of the parameter value.Notes:
- Query parameters should only be captured when
db.query.textis parameterized with placeholders. If a parameter has no name and instead is referenced only by index, then<key>SHOULD be the 0-based index.
- Query parameters should only be captured when
-
DB_QUERY_TEXT
The database query being executed.Notes:
- For sanitization see Sanitization of
db.query.text. For batch operations, if the individual operations are known to have the same query text then that query text SHOULD be used, otherwise all of the individual query texts SHOULD be concatenated with separator;or some other database system specific separator if more applicable. Even though parameterized query text can potentially have sensitive data, by using a parameterized query the user is giving a strong signal that any sensitive data will be passed as parameter values, and the benefit to observability of capturing the static part of the query text by default outweighs the risk.
- For sanitization see Sanitization of
-
DB_REDIS_DATABASE_INDEX
@Deprecated public static final io.opentelemetry.api.common.AttributeKey<Long> DB_REDIS_DATABASE_INDEXDeprecated.Deprecated, use `db.namespace` instead.Deprecated, usedb.namespaceinstead. -
DB_SQL_TABLE
Deprecated.Deprecated, use `db.collection.name` instead.Deprecated, usedb.collection.nameinstead. -
DB_STATEMENT
Deprecated.The database statement being executed.The database statement being executed. -
DB_SYSTEM
The database management system (DBMS) product as identified by the client instrumentation.Notes:
- The actual DBMS may differ from the one identified by the client. For example, when using
PostgreSQL client libraries to connect to a CockroachDB, the
db.systemis set topostgresqlbased on the instrumentation's best knowledge.
- The actual DBMS may differ from the one identified by the client. For example, when using
PostgreSQL client libraries to connect to a CockroachDB, the
-
DB_USER
Deprecated.Deprecated, no replacement at this time.Deprecated, no replacement at this time.
-