Documentation

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

The full invoked ARN as provided on the Context passed to the function (Lambda-Runtime-Invoked-Function-Arn header on the /runtime/invocation/next applicable).

Notes

This may be different from faas.id if an alias is involved.

The https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#id uniquely identifies the event.

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

The https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#specversion which the event uses.

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

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

Parent-child Reference type

Notes

The causal relationship between a child Span and a parent Span.

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

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

Username for accessing the database.

The fully-qualified class name of the https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/ driver used to connect.

This attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).

Notes

In some SQL databases, the database name to be used is called "schema name". In case there are multiple layers that could be considered for database name (e.g. Oracle instance name and schema name), the database name to be used is the more specific layer (e.g. Oracle schema name).

The database statement being executed.

Notes

The value may be sanitized to exclude sensitive information.

The name of the operation being executed, e.g. the https://docs.mongodb.com/manual/reference/command/#database-operations 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 Microsoft SQL Server https://docs.microsoft.com/en-us/sql/connect/jdbc/building-the-connection-url?view=sql-server-ver15 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 fetch size used for paging, i.e. how many rows will be returned at once.

The consistency level of the query. Based on consistency values from https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/dml/dmlConfigConsistency.html.

The name of the primary table that the operation is acting upon, including the keyspace name (if applicable).

Notes

This mirrors the db.sql.table attribute but references cassandra rather than sql. It is not recommended to attempt any client-side parsing of db.statement just to get this property, but it should be set if it is provided by the library being instrumented. If the operation is acting upon an anonymous table, or more than one table, this value MUST NOT be set.

Whether or not the query is idempotent.

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

The ID of the coordinating node for a query.

The data center of the coordinating node for a query.

The index of the database being accessed as used in the https://redis.io/commands/select, provided as an integer. To be used instead of the generic db.name attribute.

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

The name of the primary table that the operation is acting upon, including the database name (if applicable).

Notes

It is not recommended to attempt any client-side parsing of db.statement just to get this property, but it should be set if it is provided by the library being instrumented. If the operation is acting upon an anonymous table, or more than one table, this value MUST NOT be set.

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.

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.

SHOULD be set to true if the exception event is recorded at a point where it is known that the exception is escaping the scope of the span.

Notes

An exception is considered to have escaped (or left) the scope of a span, if that span is ended while the exception is still logically "in flight". This may be actually "in flight" in some languages (e.g. if the exception is passed to a Context manager's exit method in Python) but will usually be caught at the point of recording the exception in most languages.It is usually not possible to determine at the point where an exception is thrown whether it will escape the scope of a span. However, it is trivial to know that an exception will escape, if one checks for an active exception just before ending the span, as done in the #recording-an-exception.It follows that an exception may still escape the scope of the span even if the exception.escaped attribute was not set or set to false, since the event might have been recorded at a time where it was not clear whether the exception will escape.

Type of the trigger which caused this function execution.

Notes

For the server/consumer span on the incoming side, faas.trigger MUST be set.Clients invoking FaaS instances usually cannot set faas.trigger, since they would typically need to look in the payload to determine the event type. If clients set it, it should be the same as the trigger that corresponding incoming would have (i.e., this has nothing to do with the underlying transport used to make the API call to invoke the lambda, which is often HTTP).

The execution ID of the current function execution.

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.

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

A string containing the time when the data was accessed in the https://www.iso.org/iso-8601-date-and-time-format.html format expressed in https://www.w3.org/TR/NOTE-datetime.

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.

A string containing the function invocation time in the https://www.iso.org/iso-8601-date-and-time-format.html format expressed in https://www.w3.org/TR/NOTE-datetime.

A string containing the schedule period as https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm.

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

The name of the invoked function.

Notes

SHOULD be equal to the faas.name resource attribute of the invoked function.

The cloud provider of the invoked function.

Notes

SHOULD be equal to the cloud.provider resource attribute of the invoked function.

The cloud region of the invoked function.

Notes

SHOULD be equal to the cloud.region resource attribute of the invoked function.

Transport protocol used. See note below.

Remote address of the peer (dotted decimal for IPv4 or https://tools.ietf.org/html/rfc5952 for IPv6)

Remote port number.

Remote hostname or similar, see note below.

Notes

net.peer.name SHOULD NOT be set if capturing it would require an extra DNS lookup.

Like net.peer.ip but for the host IP. Useful in case of a multi-IP host.

Like net.peer.port but for the host port.

Local hostname or similar, see note below.

The internet connection type currently being used by the host.

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 name of the mobile carrier.

The mobile carrier country code.

The mobile carrier network code.

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

The ../../resource/semantic_conventions/README.md#service of the remote service. SHOULD be equal to the actual service.name resource attribute of the remote service if any.

Username or client_id extracted from the access token or https://tools.ietf.org/html/rfc7235#section-4.2 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 https://tools.ietf.org/html/rfc6749#section-3.3 or an attribute value in a http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html.

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

Current thread name.

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

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 source code file name that identifies the code unit as uniquely as possible (preferably an absolute file path).

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

HTTP request method.

Full HTTP request URL in the form scheme://host[:port]/path?query[#fragment]. Usually the fragment is not transmitted over HTTP, but if it is known, it should be included nevertheless.

Notes

http.url MUST NOT contain credentials passed via URL in form of https://username:passwordwww.example.com/. In such case the attribute's value should be https://www.example.com/@.

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

The value of the https://tools.ietf.org/html/rfc7230#section-5.4. An empty Host header should also be reported, see note.

Notes

When the header is present but empty the attribute SHOULD be set to the empty string. Note that this is a valid situation that is expected in certain cases, according the aforementioned https://tools.ietf.org/html/rfc7230#section-5.4. When the header is not set the attribute MUST NOT be set.

The URI scheme identifying the used protocol.

https://tools.ietf.org/html/rfc7231#section-6.

Kind of HTTP protocol used.

Notes

If net.transport is not specified, it can be assumed to be IP.TCP except if http.flavor is QUIC, in which case IP.UDP is assumed.

Value of the https://tools.ietf.org/html/rfc7231#section-5.5.3 header sent by the client.

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 https://tools.ietf.org/html/rfc7230#section-3.3.2 header. For requests using transport encoding, this should be the compressed size.

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

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 https://tools.ietf.org/html/rfc7230#section-3.3.2 header. For requests using transport encoding, this should be the compressed size.

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

The ordinal number of request re-sending attempt.

The primary server name of the matched virtual host. This should be obtained via configuration. If no such configuration can be obtained, this attribute MUST NOT be set ( net.host.name should be used instead).

Notes

http.url is usually not readily available on the server side but would have to be assembled in a cumbersome and sometimes lossy process from other information (see e.g. open-telemetryopentelemetry-pythonpull/148). It is thus preferred to supply the raw data that is available.

The matched route (path template).

The IP address of the original client behind all proxies, if known (e.g. from https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For).

Notes

This is not necessarily the same as net.peer.ip, 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.peer.ip, is available even if that other source just confirms the same value as net.peer.ip. Rationale: For net.peer.ip, 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.peer.ip means that one is at least somewhat confident that the address is not that of the closest proxy.

The keys in the RequestItems object field.

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

The JSON-serialized value of the ItemCollectionMetrics response field.

The value of the ProvisionedThroughput.ReadCapacityUnits request parameter.

The value of the ProvisionedThroughput.WriteCapacityUnits request parameter.

The value of the ConsistentRead request parameter.

The value of the ProjectionExpression request parameter.

The value of the Limit request parameter.

The value of the AttributesToGet request parameter.

The value of the IndexName request parameter.

The value of the Select request parameter.

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

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

The value of the ExclusiveStartTableName request parameter.

The the number of items in the TableNames response parameter.

The value of the ScanIndexForward request parameter.

The value of the Segment request parameter.

The value of the TotalSegments request parameter.

The value of the Count response parameter.

The value of the ScannedCount response parameter.

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

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

A string identifying the messaging system.

The message destination name. This might be equal to the span name but is required nevertheless.

The kind of message destination

A boolean that is true if the message destination is temporary.

The name of the transport protocol.

The version of the transport protocol.

Connection string.

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

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

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.

The compressed size of the message payload in bytes.

A string identifying the kind of message consumption as defined in the #operation-names section above. If the operation is "send", this attribute MUST NOT be set, since the operation can be inferred from the span kind in that case.

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.

RabbitMQ message routing key.

Message keys in Kafka are used for grouping alike messages to ensure they're processed on the same partition. They differ from messaging.message_id in that they're not unique. If the key is null, the attribute MUST NOT be set.

Notes

If the key type is not string, it's string representation has to be supplied for the attribute. If the key has no unambiguous, canonical string form, don't include its value.

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

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

Partition the message is sent to.

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

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

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.

Type of message.

The secondary classifier of message besides topic.

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

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

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

The full (logical) name of the service being called, including its package name, if applicable.

Notes

This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The code.namespace attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).

The name of the (logical) method being called, must be equal to the $method part in the span name.

Notes

This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The code.function attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).

The https://github.com/grpc/grpc/blob/v1.33.2/doc/statuscodes.md of the gRPC request.

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

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.

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

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

Whether this is a received or sent message.

MUST be calculated as two different counters starting from 1 one for sent messages and one for received message.

Notes

This way we guarantee that the values will be consistent between different implementations.

Compressed size of the message in bytes.

Uncompressed size of the message in bytes.

The name of the keyspace being accessed.

Deprecated: This item has been removed as of 1.8.0 of the semantic conventions. Please use DB_NAME instead.

The HBase namespace being accessed.

Deprecated: This item has been removed as of 1.8.0 of the semantic conventions. Please use DB_NAME instead.