You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/attributes-registry/messaging.md
+10-9
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Attributes describing telemetry around messaging systems and messaging activitie
35
35
|`messaging.message.envelope.size`| int | The size of the message body and metadata in bytes. [7]|`2738`||
36
36
|`messaging.message.id`| string | A value used by the messaging system as an identifier for the message, represented as a string. |`452a7c7c7c7048c2f887f61572b18fc2`||
37
37
|`messaging.operation.name`| string | The system-specific name of the messaging operation. |`ack`; `nack`; `send`||
38
-
|`messaging.operation.type`| string | A string identifying the type of the messaging operation. [8]|`publish`; `create`; `receive`||
38
+
|`messaging.operation.type`| string | A string identifying the type of the messaging operation. [8]|`create`; `send`; `receive`||
39
39
|`messaging.system`| string | The messaging system as identified by the client instrumentation. [9]|`activemq`; `aws_sqs`; `eventgrid`||
40
40
41
41
**[1]:** 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.
@@ -61,14 +61,15 @@ size should be used.
61
61
62
62
`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.
|`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 publishing scenarios. ||
67
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
68
-
|`process`| One or more messages are processed by a consumer. ||
69
-
|`publish`| One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. ||
70
-
|`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. ||
71
-
|`settle`| One or more messages are settled. ||
|`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. ||
67
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
68
+
|`process`| One or more messages are processed by a consumer. ||
69
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
70
+
|`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. ||
71
+
|`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. ||
72
+
|`settle`| One or more messages are settled. ||
72
73
73
74
`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.
Copy file name to clipboardexpand all lines: docs/messaging/azure-messaging.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The following additional attributes are defined:
29
29
|[`messaging.batch.message_count`](/docs/attributes-registry/messaging.md)| int | The number of messages sent, received, or processed in the scope of the batching operation. [3]|`0`; `1`; `2`|`Conditionally Required`[4]||
30
30
|[`messaging.destination.name`](/docs/attributes-registry/messaging.md)| string | The message destination name [5]|`MyQueue`; `MyTopic`|`Conditionally Required`[6]||
31
31
|[`messaging.destination.subscription.name`](/docs/attributes-registry/messaging.md)| string | Azure Service Bus [subscription name](https://learn.microsoft.com/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions). |`subscription-a`|`Conditionally Required` If messages are received from the subscription. ||
32
-
|[`messaging.operation.type`](/docs/attributes-registry/messaging.md)| string | A string identifying the type of the messaging operation. [7]|`publish`; `create`; `receive`|`Conditionally Required` If applicable. ||
32
+
|[`messaging.operation.type`](/docs/attributes-registry/messaging.md)| string | A string identifying the type of the messaging operation. [7]|`send`; `create`; `receive`|`Conditionally Required` If applicable. ||
33
33
|[`messaging.servicebus.disposition_status`](/docs/attributes-registry/messaging.md)| string | Describes the [settlement type](https://learn.microsoft.com/azure/service-bus-messaging/message-transfers-locks-settlement#peeklock). |`complete`; `abandon`; `dead_letter`|`Conditionally Required` if and only if `messaging.operation` is `settle`. ||
34
34
|[`messaging.servicebus.message.delivery_count`](/docs/attributes-registry/messaging.md)| int | Number of deliveries that have been attempted for this message. |`2`|`Conditionally Required`[8]||
35
35
|[`server.address`](/docs/attributes-registry/server.md)| 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`|`Conditionally Required` If available. ||
@@ -109,10 +109,10 @@ and SHOULD be provided **at span creation time** (if provided at all):
109
109
110
110
| Value | Description | Stability |
111
111
|---|---|---|
112
-
|`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 publishing scenarios. ||
112
+
|`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. ||
113
113
|`process`| One or more messages are processed by a consumer. ||
114
-
|`publish`| One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. ||
115
114
|`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. ||
115
+
|`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. ||
116
116
|`settle`| One or more messages are settled. ||
117
117
118
118
@@ -154,7 +154,7 @@ The following additional attributes are defined:
154
154
|[`messaging.consumer.group.name`](/docs/attributes-registry/messaging.md)| string | Azure Event Hubs [consumer group name](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-features#consumer-groups). |`my-group`; `indexer`|`Conditionally Required` On consumer spans. ||
155
155
|[`messaging.destination.name`](/docs/attributes-registry/messaging.md)| string | The message destination name [5]|`MyQueue`; `MyTopic`|`Conditionally Required`[6]||
156
156
|[`messaging.destination.partition.id`](/docs/attributes-registry/messaging.md)| string | String representation of the partition id messages are sent to or received from, unique within the Event Hub. |`1`|`Conditionally Required` If available. ||
157
-
|[`messaging.operation.type`](/docs/attributes-registry/messaging.md)| string | A string identifying the type of the messaging operation. [7]|`publish`; `create`; `receive`|`Conditionally Required` If applicable. ||
157
+
|[`messaging.operation.type`](/docs/attributes-registry/messaging.md)| string | A string identifying the type of the messaging operation. [7]|`send`; `create`; `receive`|`Conditionally Required` If applicable. ||
158
158
|[`server.address`](/docs/attributes-registry/server.md)| string | Server domain name if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name. [8]|`example.com`; `10.1.2.80`; `/tmp/my.sock`|`Conditionally Required` If available. ||
159
159
|[`messaging.eventhubs.message.enqueued_time`](/docs/attributes-registry/messaging.md)| int | The UTC epoch seconds at which the message has been accepted and stored in the entity. |`1701393730`|`Recommended`||
160
160
|[`messaging.message.id`](/docs/attributes-registry/messaging.md)| string | A value used by the messaging system as an identifier for the message, represented as a string. |`452a7c7c7c7048c2f887f61572b18fc2`|`Recommended` If span describes operation on a single message. ||
@@ -231,10 +231,10 @@ and SHOULD be provided **at span creation time** (if provided at all):
231
231
232
232
| Value | Description | Stability |
233
233
|---|---|---|
234
-
|`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 publishing scenarios. ||
234
+
|`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. ||
235
235
|`process`| One or more messages are processed by a consumer. ||
236
-
|`publish`| One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the "Publish" span can be used as the creation context and no "Create" span needs to be created. ||
237
236
|`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. ||
237
+
|`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. ||
238
238
|`settle`| One or more messages are settled. ||
0 commit comments