SemanticAttributes

The JSON-serialized value of each item in the AttributeDefinitions request field.

The value of the AttributesToGet request parameter.

The value of the ConsistentRead request parameter.

The JSON-serialized value of each item in the ConsumedCapacity response field.

The value of the Count response parameter.

The value of the ExclusiveStartTableName request parameter.

The JSON-serialized value of each item in the the GlobalSecondaryIndexUpdates request field.

The JSON-serialized value of each item of the GlobalSecondaryIndexes request field

The value of the IndexName request parameter.

The JSON-serialized value of the ItemCollectionMetrics response field.

The value of the Limit request parameter.

The JSON-serialized value of each item of the LocalSecondaryIndexes request field.

The value of the ProjectionExpression request parameter.

The value of the ProvisionedThroughput.ReadCapacityUnits request parameter.

The value of the ProvisionedThroughput.WriteCapacityUnits request parameter.

The value of the ScanIndexForward request parameter.

The value of the ScannedCount response parameter.

The value of the Segment request parameter.

The value of the Select request parameter.

The the number of items in the TableNames response parameter.

The keys in the RequestItems object field.

The value of the TotalSegments request parameter.

The <a href="https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#id">event_id uniquely identifies the event.

The <a href="https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#source-1">source identifies the context in which an event happened.

The <a href="https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#specversion">version of the CloudEvents specification which the event uses.

The <a href="https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#subject">subject of the event in the context of the event producer (identified by source).

The <a href="https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#type">event_type contains a value describing the type of event related to the originating occurrence.

The column number in code.filepath best representing the operation. It SHOULD point within the code unit named in code.function.

The source code file name that identifies the code unit as uniquely as possible (preferably an absolute file path).

The method or function name, or equivalent (usually rightmost part of the code unit's name).

The line number in code.filepath best representing the operation. It SHOULD point within the code unit named in code.function.

The "namespace" within which code.function is defined. Usually the qualified class or module name, such that code.namespace + some separator + code.function form a unique identifier for the code unit.

The consistency level of the query. Based on consistency values from <a href="https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/dml/dmlConfigConsistency.html">CQL.

The data center of the coordinating node for a query.

The ID of the coordinating node for a query.

Whether or not the query is idempotent.

The fetch size used for paging, i.e. how many rows will be returned at once.

The number of times a query was speculatively executed. Not set or 0 if the query was not executed speculatively.

The connection string used to connect to the database. It is recommended to remove embedded credentials.

The fully-qualified class name of the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/">Java Database Connectivity (JDBC) driver used to connect.

The collection being accessed within the database stated in db.name.

The Microsoft SQL Server <a href="https://docs.microsoft.com/en-us/sql/connect/jdbc/building-the-connection-url?view=sql-server-ver15">instance name connecting to. This name is used to determine the port of a named instance. Notes: - If setting a db.mssql.instance_name, net.peer.port is no longer required (but still recommended if non-standard).

The name of the operation being executed, e.g. the <a href="https://docs.mongodb.com/manual/reference/command/#database-operations">MongoDB command name such as findAndModify, or the SQL keyword. Notes: - When setting this to an SQL keyword, it is not recommended to attempt any client-side parsing of db.statement just to get this property, but it should be set if the operation name is provided by the library being instrumented. If the SQL statement has an ambiguous operation, or performs more than one operation, this value may be omitted.

The index of the database being accessed as used in the <a href="https://redis.io/commands/select">SELECT command, provided as an integer. To be used instead of the generic db.name attribute.

An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.

Username for accessing the database.

Username or client_id extracted from the access token or <a href="https://tools.ietf.org/html/rfc7235#section-4.2">Authorization header in the inbound request from outside the system.

Actual/assumed role the client is making the request under extracted from token or application security context.

Scopes or granted authorities the client currently possesses extracted from token or application security context. The value would come from the scope associated with an <a href="https://tools.ietf.org/html/rfc6749#section-3.3">OAuth 2.0 Access Token or an attribute value in a SAML 2.0 Assertion.

The name identifies the event.

The exception message.

A stacktrace as a string in the natural representation for the language runtime. The representation is to be determined and documented by each language SIG.

The type of the exception (its fully-qualified class name, if applicable). The dynamic type of the exception should be preferred over the static type in languages that support it.

A boolean that is true if the serverless function is executed for the first time (aka cold-start).

A string containing the schedule period as <a href="https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm">Cron Expression.

The name of the source on which the triggering operation was performed. For example, in Cloud Storage or S3 corresponds to the bucket name, and in Cosmos DB to the database name.

The document name/table subjected to the operation. For example, in Cloud Storage or S3 is the name of the file, and in Cosmos DB the table name.

Describes the type of the operation that was performed on the data.

A string containing the time when the data was accessed in the <a href="https://www.iso.org/iso-8601-date-and-time-format.html">ISO 8601 format expressed in UTC.

The invocation ID of the current function invocation.

A string containing the function invocation time in the <a href="https://www.iso.org/iso-8601-date-and-time-format.html">ISO 8601 format expressed in UTC.

The unique identifier of the feature flag.

The name of the service provider that performs the flag evaluation.

The name of the operation being executed.

The type of the operation being executed.

The IP address of the original client behind all proxies, if known (e.g. from <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For">X-Forwarded-For). Notes: - This is not necessarily the same as net.sock.peer.addr, which would identify the network-level peer, which may be a proxy. - This attribute should be set when a source of information different from the one used for net.sock.peer.addr, is available even if that other source just confirms the same value as net.sock.peer.addr. Rationale: For net.sock.peer.addr, one typically does not know if it comes from a proxy, reverse proxy, or the actual client. Setting http.client_ip when it's the same as net.sock.peer.addr means that one is at least somewhat confident that the address is not that of the closest proxy.

Kind of HTTP protocol used.

HTTP request method.

The size of the request payload body in bytes. This is the number of bytes transferred excluding headers and is often, but not always, present as the <a href="https://www.rfc-editor.org/rfc/rfc9110.html#field.content-length">Content-Length header. For requests using transport encoding, this should be the compressed size.

The size of the response payload body in bytes. This is the number of bytes transferred excluding headers and is often, but not always, present as the <a href="https://www.rfc-editor.org/rfc/rfc9110.html#field.content-length">Content-Length header. For requests using transport encoding, this should be the compressed size.

The URI scheme identifying the used protocol.

HTTP response status code.

The full request target as passed in a HTTP request line or equivalent.

Compressed size of the message in bytes.

Whether this is a received or sent message.

Uncompressed size of the message in bytes.

The identifier for the consumer receiving a message. For Kafka, set it to {messaging.kafka.consumer.group - {messaging.kafka.client_id}}, if both are present, or only messaging.kafka.consumer.group. For brokers, such as RabbitMQ and Artemis, set it to the client_id of the client consuming the message.

A boolean that is true if the message destination is anonymous (could be unnamed or have auto-generated name).

The kind of message destination

A boolean that is true if the message destination is temporary and might not exist anymore after messages are processed.

Client Id for the Consumer or Producer that is handling the message.

Name of the Kafka Consumer Group that is handling the message. Only applies to consumers, not producers.

Partition the message is sent to.

The offset of a record in the corresponding Kafka partition.

A boolean that is true if the message is a tombstone.

Partition the message is received from.

The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called "Correlation ID".

A value used by the messaging system as an identifier for the message, represented as a string.

The compressed size of the message payload in bytes.

The (uncompressed) size of the message payload in bytes. Also use this attribute if it is unknown whether the compressed or uncompressed payload size is reported.

A string identifying the kind of messaging operation as defined in the <a href="#operation-names">Operation names section above. Notes: - If a custom value is used, it MUST be of low cardinality.

RabbitMQ message routing key.

Name of the RocketMQ producer/consumer group that is handling the message. The client type is identified by the SpanKind.

The unique identifier for each client.

Model of message consumption. This only applies to consumer spans.

The delay time level for delay message, which determines the message delay time.

The timestamp in milliseconds that the delay message is expected to be delivered to consumer.

It is essential for FIFO message. Messages that belong to the same message group are always processed one by one within the same consumer group.

Key(s) of message, another way to mark message besides message id.

The secondary classifier of message besides topic.

Type of message.

Namespace of RocketMQ resources, resources in different namespaces are individual.

A boolean that is true if the message source is anonymous (could be unnamed or have auto-generated name).

The kind of message source

A boolean that is true if the message source is temporary and might not exist anymore after messages are processed.

A string identifying the messaging system.

Application layer protocol used. The value SHOULD be normalized to lowercase.

The ISO 3166-1 alpha-2 2-character country code associated with the mobile carrier network.

The mobile carrier country code.

The mobile carrier network code.

The name of the mobile carrier.

This describes more details regarding the connection.type. It may be the type of cell technology connection, but it could be used for describing details about a wifi connection.

The internet connection type currently being used by the host.

Logical local hostname or similar, see note below.

Logical local port number, preferably the one that the peer used to connect

Logical remote port number

Protocol <a href="https://man7.org/linux/man-pages/man7/address_families.7.html">address family which is used for communication.

Local socket address. Useful in case of a multi-IP host.

Local socket port number.

Remote socket peer address: IPv4 or IPv6 for internet protocols, path for local communication, <a href="https://man7.org/linux/man-pages/man7/address_families.7.html">etc.

Remote socket peer name.

Remote socket peer port.

Transport protocol used. See note below.

Name of the code, either "OK" or "ERROR". MUST NOT be set if the status code is UNSET.

Description of the Status if it has a value, otherwise not set.

The service.name of the remote service. SHOULD be equal to the actual service.name resource attribute of the remote service if any.

The error codes of the Connect request. Error codes are always string values.

The <a href="https://github.com/grpc/grpc/blob/v1.33.2/doc/statuscodes.md">numeric status code of the gRPC request.

error.code property of response if it is an error response.

error.message property of response if it is an error response.

id property of request or response. Since protocol allows id to be int, string, null or missing (for notifications), value is expected to be cast to string for simplicity. Use empty string in case of null value. Omit entirely if this is a notification.

Protocol version as in jsonrpc property of request/response. Since JSON-RPC 1.0 does not specify this, the value can be omitted.

A string identifying the remoting system. See below for a list of well-known identifiers.

The URL of the OpenTelemetry schema for these keys and values.

Current "managed" thread ID (as opposed to OS thread ID).

Current thread name.

Value of the <a href="https://www.rfc-editor.org/rfc/rfc9110.html#field.user-agent">HTTP User-Agent header sent by the client.

The name of the keyspace being accessed.

The HBase namespace being accessed.

The execution ID of the current function execution.

The size of the uncompressed request payload body after transport decoding. Not set if transport encoding not used.

The ordinal number of request re-sending attempt.

Value of the <a href="https://www.rfc-editor.org/rfc/rfc9110.html#field.user-agent">HTTP User-Agent header sent by the client.

The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called "Correlation ID".

A string identifying the messaging system.

Partition the message is received from.

A boolean that is true if the message is a tombstone.

The name of the transport protocol.