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/messaging/azure-messaging.md
+20-4Lines changed: 20 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,13 +139,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
139
139
| Value | Description | Stability |
140
140
|---|---|---|
141
141
|`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. ||
142
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
143
142
|`process`| One or more messages are processed by a consumer. ||
144
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
145
143
|`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. ||
146
144
|`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. ||
147
145
|`settle`| One or more messages are settled. ||
148
146
147
+
<details>
148
+
<summary><b>Past Defined Values:</b></summary>
149
+
150
+
| Value | Description | Deprecation Explanation |
151
+
|---|---|---|
152
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
153
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
154
+
155
+
</details>
156
+
149
157
---
150
158
151
159
`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.
@@ -263,13 +271,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
263
271
| Value | Description | Stability |
264
272
|---|---|---|
265
273
|`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. ||
266
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
267
274
|`process`| One or more messages are processed by a consumer. ||
268
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
269
275
|`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. ||
270
276
|`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. ||
271
277
|`settle`| One or more messages are settled. ||
272
278
279
+
<details>
280
+
<summary><b>Past Defined Values:</b></summary>
281
+
282
+
| Value | Description | Deprecation Explanation |
283
+
|---|---|---|
284
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
285
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
Copy file name to clipboardExpand all lines: docs/messaging/gcp-pubsub.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,13 +134,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
134
134
| Value | Description | Stability |
135
135
|---|---|---|
136
136
|`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. ||
137
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
138
137
|`process`| One or more messages are processed by a consumer. ||
139
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
140
138
|`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. ||
141
139
|`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. ||
142
140
|`settle`| One or more messages are settled. ||
143
141
142
+
<details>
143
+
<summary><b>Past Defined Values:</b></summary>
144
+
145
+
| Value | Description | Deprecation Explanation |
146
+
|---|---|---|
147
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
148
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
Copy file name to clipboardExpand all lines: docs/messaging/kafka.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,13 +143,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
143
143
| Value | Description | Stability |
144
144
|---|---|---|
145
145
|`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. ||
146
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
147
146
|`process`| One or more messages are processed by a consumer. ||
148
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
149
147
|`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. ||
150
148
|`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. ||
151
149
|`settle`| One or more messages are settled. ||
152
150
151
+
<details>
152
+
<summary><b>Past Defined Values:</b></summary>
153
+
154
+
| Value | Description | Deprecation Explanation |
155
+
|---|---|---|
156
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
157
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
Copy file name to clipboardExpand all lines: docs/messaging/messaging-metrics.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,13 +139,21 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
139
139
| Value | Description | Stability |
140
140
|---|---|---|
141
141
|`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. ||
142
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
143
142
|`process`| One or more messages are processed by a consumer. ||
144
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
145
143
|`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. ||
146
144
|`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. ||
147
145
|`settle`| One or more messages are settled. ||
148
146
147
+
<details>
148
+
<summary><b>Past Defined Values:</b></summary>
149
+
150
+
| Value | Description | Deprecation Explanation |
151
+
|---|---|---|
152
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
153
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
154
+
155
+
</details>
156
+
149
157
---
150
158
151
159
`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/messaging-spans.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -485,13 +485,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
485
485
| Value | Description | Stability |
486
486
|---|---|---|
487
487
|`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. ||
488
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
489
488
|`process`| One or more messages are processed by a consumer. ||
490
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
491
489
|`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. ||
492
490
|`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. ||
493
491
|`settle`| One or more messages are settled. ||
494
492
493
+
<details>
494
+
<summary><b>Past Defined Values:</b></summary>
495
+
496
+
| Value | Description | Deprecation Explanation |
497
+
|---|---|---|
498
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
499
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
500
+
501
+
</details>
502
+
495
503
---
496
504
497
505
`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.
0 commit comments