Semantic conventions for Azure messaging systems
Status: Development
The Semantic Conventions for Azure Service Bus and Azure Event Hubs extend and override the Messaging Semantic Conventions.
Existing messaging instrumentations that are using v1.24.0 of this document (or prior):
- SHOULD NOT change the version of the messaging conventions that they emit by default until the messaging semantic conventions are marked stable. Conventions include, but are not limited to, attributes, metric and span names, span kind and unit of measure.
- SHOULD introduce an environment variable
OTEL_SEMCONV_STABILITY_OPT_INin the existing major version as a comma-separated list of category-specific values (e.g., http, databases, messaging). The list of values includes:messaging- emit the new, stable messaging conventions, and stop emitting the old experimental messaging conventions that the instrumentation emitted previously.messaging/dup- emit both the old and the stable messaging conventions, allowing for a seamless transition.- The default behavior (in the absence of one of these values) is to continue emitting whatever version of the old experimental messaging conventions the instrumentation was emitting previously.
- Note:
messaging/duphas higher precedence thanmessagingin case both values are present
- SHOULD maintain (security patching at a minimum) the existing major version for at least six months after it starts emitting both sets of conventions.
- SHOULD drop the environment variable in the next major version.
- SHOULD emit the new, stable values for span name, span kind and similar “single”
valued concepts when
messaging/dupis present in the list.
Azure Service Bus
Create span
Status:
Describes a message being created for sending to Azure Service Bus.
“Create” spans always refer to a single message and are used to provide a unique
creation context for messages in batch sending scenarios. A “Create” span is only
used together with a client “Send” span (messaging.send.client) that links to it;
when the “Send” span itself serves as the creation context, use the producer “Send”
span (messaging.send.producer) instead and omit the “Create” span. See
Producer spans for details.
Span kind SHOULD be PRODUCER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name |  | Required | string | Azure Service Bus operation name. [1] | create |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type |  | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.destination.name | | Conditionally Required [4] | string | The message destination name [5] | MyQueue; MyTopic |
messaging.destination.template | | Conditionally Required [6] | string | Low cardinality representation of the messaging destination name [7] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [8] | create |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [9] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [10] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [11] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [12] | 2738 |
[1] messaging.operation.name: SHOULD be set to create.
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[5] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[6] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[7] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[8] messaging.operation.type: SHOULD be set to create.
[9] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[10] server.port: 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.
[11] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[12] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Send span (producer)
Status:
Describes a producer sending one or more messages to Azure Service Bus.
Use this span when no separate “Create” span exists and the “Send” span’s context is injected into the message(s) as the creation context. See Producer spans for details.
Span kind SHOULD be PRODUCER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | send; schedule |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | send |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD match one of the following values:
sendschedule
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to send.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Send span (client)
Status:
Describes a producer sending one or more messages to Azure Service Bus.
Use this span when a “Create” span (or a custom creation context) already exists for the message(s): the “Send” span describes only the transport operation and links to the creation context that was injected into the message. See Producer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | send; schedule |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | send |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD match one of the following values:
sendschedule
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to send.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Receive span
Status:
Describes a consumer receiving one or more messages from Azure Service Bus.
“Receive” spans are created for pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. See Consumer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | receive; peek; receive_deferred |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.subscription.name | | Conditionally Required If messages are received from the subscription. | string | Azure Service Bus subscription name. | subscription-a |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | receive |
messaging.servicebus.message.delivery_count | | Conditionally Required [11] | int | Number of deliveries that have been attempted for this message. | 2 |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
messaging.servicebus.message.enqueued_time | | Recommended | int | The UTC epoch seconds at which the message has been accepted and stored in the entity. | 1701393730 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [12] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [13] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [14] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [15] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [16] | 2738 |
[1] messaging.operation.name: SHOULD match one of the following values:
receivepeekreceive_deferred
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to receive.
[11] messaging.servicebus.message.delivery_count: If delivery count is available and is bigger than 0.
[12] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[13] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[14] server.port: 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.
[15] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[16] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.subscription.namemessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Process span
Status:
Describes a consumer processing one or more messages from Azure Service Bus (push-based).
“Process” spans are created for push-based scenarios, where messages are passed to the application through a callback or handler. See Consumer spans for details.
Exclusively for single-message scenarios, when the message creation context is used as the parent, see Message creation context as parent of “Process” span.
Span kind SHOULD be CONSUMER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | process |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.subscription.name | | Conditionally Required If messages are received from the subscription. | string | Azure Service Bus subscription name. | subscription-a |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | process |
messaging.servicebus.message.delivery_count | | Conditionally Required [11] | int | Number of deliveries that have been attempted for this message. | 2 |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
messaging.servicebus.message.enqueued_time | | Recommended | int | The UTC epoch seconds at which the message has been accepted and stored in the entity. | 1701393730 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD be set to process.
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to process.
[11] messaging.servicebus.message.delivery_count: If delivery count is available and is bigger than 0.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.subscription.namemessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Settle span
Status:
Describes settling (complete/abandon/defer/dead-letter) one or more Azure Service Bus messages.
“Settle” spans are created for every manually or automatically triggered settlement operation. See Consumer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | complete; abandon; dead_letter |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.subscription.name | | Conditionally Required If messages are received from the subscription. | string | Azure Service Bus subscription name. | subscription-a |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | settle |
messaging.servicebus.disposition_status | | Conditionally Required [11] | string | Describes the settlement type. | complete; abandon; dead_letter |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [12] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [13] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [14] | 80; 8080; 443 |
[1] messaging.operation.name: SHOULD match one of the following values:
abandoncompletedeferdead_letterdelete
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to settle.
[11] messaging.servicebus.disposition_status: If the message is settled with a specific disposition status.
[12] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[13] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[14] server.port: 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.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.subscription.namemessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.servicebus.disposition_status 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 |
|---|---|---|
abandon | Message is abandoned | |
complete | Message is completed | |
dead_letter | Message is sent to dead letter queue | |
defer | Message is deferred | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Generic client span
Status:
Describes an Azure Service Bus client operation that is not covered by a more specific (create, send, receive, process, or settle) span.
Catch-all span for Azure Service Bus client operations - such as session management or lock renewal - that do not map to a create, send, receive, process, or settle span.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Service Bus operation name. [1] | accept_session; renew_message_lock; create_transaction |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | servicebus |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | MessageLockLost; MessagingEntityNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyQueue; MyTopic |
messaging.destination.subscription.name | | Conditionally Required If messages are received from the subscription. | string | Azure Service Bus subscription name. | subscription-a |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | create; send; receive |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.destination.partition.id | | Recommended When applicable. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.message.conversation_id | | Recommended | string | Message correlation ID property. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
[1] messaging.operation.name: SHOULD be set to the name of the client method in snake_case, for example:
- session operations:
accept_session,get_session_state,set_session_state,renew_session_lock - lock renewal:
renew_message_lock - scheduling operations:
cancel_scheduled - transaction operations:
create_transaction,commit_transaction,rollback_transaction
[2] messaging.system: MUST be set to "servicebus".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: If a custom value is used, it MUST be of low cardinality.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.subscription.namemessaging.operation.namemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Azure Event Hubs
Create span
Status:
Describes a message being created for sending to Azure Event Hubs.
“Create” spans always refer to a single message and are used to provide a unique
creation context for messages in batch sending scenarios. A “Create” span is only
used together with a client “Send” span (messaging.send.client) that links to it;
when the “Send” span itself serves as the creation context, use the producer “Send”
span (messaging.send.producer) instead and omit the “Create” span. See
Producer spans for details.
Span kind SHOULD be PRODUCER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | create |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.destination.name | | Conditionally Required [4] | string | The message destination name [5] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.destination.template | | Conditionally Required [6] | string | Low cardinality representation of the messaging destination name [7] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [8] | create |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [9] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [10] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [11] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [12] | 2738 |
[1] messaging.operation.name: SHOULD be set to create.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[5] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[6] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[7] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[8] messaging.operation.type: SHOULD be set to create.
[9] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[10] server.port: 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.
[11] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[12] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Send span (producer)
Status:
Describes a producer sending one or more messages to Azure Event Hubs.
Use this span when no separate “Create” span exists and the “Send” span’s context is injected into the message(s) as the creation context. See Producer spans for details.
Span kind SHOULD be PRODUCER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | send |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | send |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD be set to send.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to send.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Send span (client)
Status:
Describes a producer sending one or more messages to Azure Event Hubs.
Use this span when a “Create” span (or a custom creation context) already exists for the message(s): the “Send” span describes only the transport operation and links to the creation context that was injected into the message. See Producer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | send |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | send |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD be set to send.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to send.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Receive span
Status:
Describes a consumer receiving one or more messages from Azure Event Hubs (pull-based).
“Receive” spans are created for pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. See Consumer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | receive |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | receive |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.consumer.group.name | | Recommended | string | Azure Event Hubs consumer group name. | my-group; indexer |
messaging.eventhubs.message.enqueued_time | | Recommended | int | The UTC epoch seconds at which the message has been accepted and stored in the entity. | 1701393730 |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [14] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [15] | 2738 |
[1] messaging.operation.name: SHOULD be set to receive.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to receive.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
[14] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[15] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.consumer.group.namemessaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Process span
Status:
Describes a consumer processing one or more messages from Azure Event Hubs (push-based).
“Process” spans are created for push-based scenarios, where messages are passed to the application through a callback or handler. See Consumer spans for details.
Exclusively for single-message scenarios, when the message creation context is used as the parent, see Message creation context as parent of “Process” span.
Span kind SHOULD be CONSUMER.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | process |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | The identifier of the partition messages are sent to or received from, unique within the messaging.destination.name. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | process |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.consumer.group.name | | Recommended | string | Azure Event Hubs consumer group name. | my-group; indexer |
messaging.eventhubs.message.enqueued_time | | Recommended | int | The UTC epoch seconds at which the message has been accepted and stored in the entity. | 1701393730 |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [11] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [12] | 80; 8080; 443 |
messaging.message.body.size | | Opt-In | int | The size of the message body in bytes. Only applicable for spans describing single message operations. [13] | 1439 |
messaging.message.envelope.size | | Opt-In | int | The size of the message body and metadata in bytes. [14] | 2738 |
[1] messaging.operation.name: SHOULD be set to process.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to process.
[11] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[12] server.port: 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.
[13] messaging.message.body.size: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed
body size should be used.
[14] messaging.message.envelope.size: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed
size should be used.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.consumer.group.namemessaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Settle span
Status:
Describes checkpointing (settling) processed messages in Azure Event Hubs.
“Settle” spans are created for every manually or automatically triggered settlement operation. See Consumer spans for details.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | checkpoint |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | String representation of the partition ID messages are checkpointed for, unique within the Event Hub. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | settle |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.consumer.group.name | | Recommended | string | Azure Event Hubs consumer group name. | my-group; indexer |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
[1] messaging.operation.name: SHOULD be set to checkpoint.
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: SHOULD be set to settle.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.consumer.group.namemessaging.destination.namemessaging.destination.partition.idmessaging.destination.templatemessaging.operation.namemessaging.operation.typemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Generic client span
Status:
Describes an Azure Event Hubs client operation that is not covered by a more specific (create, send, receive, process, or settle) span.
Catch-all span for Azure Event Hubs client operations - such as metadata retrieval - that do not map to a create, send, receive, process, or settle span.
Span kind SHOULD be CLIENT.
Span status SHOULD follow the Recording Errors document.
Attributes:
| Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|
messaging.operation.name | | Required | string | Azure Event Hubs operation name. [1] | get_partition_properties; get_event_hub_properties |
messaging.system | | Required | string | The messaging system as identified by the client instrumentation. [2] | eventhubs |
error.type | | Conditionally Required If and only if the messaging operation has failed. | string | Describes a class of error the operation ended with. [3] | ConsumerDisconnected; ResourceNotFound; ServiceBusy |
messaging.batch.message_count | | Conditionally Required [4] | int | The number of messages sent, received, or processed in the scope of the batching operation. [5] | 0; 1; 2 |
messaging.destination.name | | Conditionally Required [6] | string | The message destination name [7] | MyTopic |
messaging.destination.partition.id | | Conditionally Required If available. | string | String representation of the partition ID, unique within the Event Hub. | 1 |
messaging.destination.template | | Conditionally Required [8] | string | Low cardinality representation of the messaging destination name [9] | /customers/{customerId} |
messaging.operation.type | | Conditionally Required If applicable. | string | A string identifying the type of the messaging operation. [10] | create; send; receive |
messaging.client.id | | Recommended | string | A unique identifier for the client that consumes or produces a message. | client-5; myhost@8742@s8083jm |
messaging.message.conversation_id | | Recommended | string | The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”. | MyConversationId |
messaging.message.id | | Recommended If span describes operation on a single message. | string | A value used by the messaging system as an identifier for the message, represented as a string. | 452a7c7c7c7048c2f887f61572b18fc2 |
network.peer.address | | Recommended If applicable for this messaging system. | string | Peer address of the messaging intermediary node where the operation was performed. [11] | 10.1.2.80; /tmp/my.sock |
network.peer.port | | Recommended if and only if network.peer.address is set. | int | Peer port of the messaging intermediary node where the operation was performed. | 65123 |
server.address | | Recommended | string | Server domain name if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name. [12] | example.com; 10.1.2.80; /tmp/my.sock |
server.port | | Recommended | int | Server port number. [13] | 80; 8080; 443 |
[1] messaging.operation.name: SHOULD be set to the name of the client method in snake_case, for example:
get_partition_propertiesget_event_hub_properties
[2] messaging.system: MUST be set to "eventhubs".
[3] error.type: The error.type SHOULD be predictable, and SHOULD have low cardinality.
When error.type is set to a type (e.g., an exception type), its
canonical class name identifying the type within the artifact SHOULD be used.
If the recorded error type is a wrapper that is not meaningful for
failure classification, instrumentation MAY use the type of the inner
error instead. For example, in Go, errors created with fmt.Errorf
using %w MAY be unwrapped when the wrapper type does not help
classify the failure.
Instrumentations SHOULD document the list of errors they report.
The cardinality of error.type within one instrumentation library SHOULD be low.
Telemetry consumers that aggregate data from multiple instrumentation libraries and applications
should be prepared for error.type to have high cardinality at query time when no
additional filters are applied.
If the operation has completed successfully, instrumentations SHOULD NOT set error.type.
If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes), it’s RECOMMENDED to:
- Use a domain-specific attribute
- Set
error.typeto capture all errors, regardless of whether they are defined within the domain-specific set or not.
[4] messaging.batch.message_count: If the span describes an operation on a batch of messages.
[5] messaging.batch.message_count: Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
[6] messaging.destination.name: If span describes operation on a single message or if the value applies to all messages in the batch.
[7] messaging.destination.name: SHOULD uniquely identify a specific queue, topic or other entity within the broker. If
the broker doesn’t have such notion, it SHOULD uniquely identify the broker.
[8] messaging.destination.template: If available. Instrumentations MUST NOT use messaging.destination.name as template unless low-cardinality of destination name is guaranteed.
[9] messaging.destination.template: Destination names could be constructed from templates. An example would be a destination name involving a username or product ID. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
[10] messaging.operation.type: If a custom value is used, it MUST be of low cardinality.
[11] network.peer.address: Semantic conventions for individual messaging systems SHOULD document whether network.peer.* attributes are applicable.
Network peer address and port are important when the application interacts with individual intermediary nodes directly,
If a messaging operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
[12] server.address: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or UNIX domain socket name.
[13] server.port: 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.
The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):
messaging.destination.namemessaging.destination.partition.idmessaging.operation.namemessaging.systemserver.addressserver.port
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. | |
messaging.operation.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 |
|---|---|---|
create | A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch sending scenarios. | |
process | One or more messages are processed by a consumer. | |
receive | One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages. | |
send | One or more messages are provided for sending to an intermediary. If a single message is sent, the context of the “Send” span can be used as the creation context and no “Create” span needs to be created. | |
settle | One or more messages are settled. | |
messaging.system 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 |
|---|---|---|
activemq | Apache ActiveMQ | |
aws.sns | Amazon Simple Notification Service (SNS) | |
aws_sqs | Amazon Simple Queue Service (SQS) | |
eventgrid | Azure Event Grid | |
eventhubs | Azure Event Hubs | |
gcp_pubsub | Google Cloud Pub/Sub | |
jms | Java Message Service | |
kafka | Apache Kafka | |
pulsar | Apache Pulsar | |
rabbitmq | RabbitMQ | |
rocketmq | Apache RocketMQ | |
servicebus | Azure Service Bus | |
Feedback
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!