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
@@ -142,13 +142,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
142
142
| Value | Description | Stability |
143
143
|---|---|---|
144
144
|`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. ||
145
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
146
145
|`process`| One or more messages are processed by a consumer. ||
147
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
148
146
|`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. ||
149
147
|`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. ||
150
148
|`settle`| One or more messages are settled. ||
151
149
150
+
<details>
151
+
<summary><b>Past Defined Values:</b></summary>
152
+
153
+
| Value | Description | Deprecation Explanation |
154
+
|---|---|---|
155
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
156
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
157
+
158
+
</details>
159
+
152
160
---
153
161
154
162
`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.
@@ -269,13 +277,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
269
277
| Value | Description | Stability |
270
278
|---|---|---|
271
279
|`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. ||
272
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
273
280
|`process`| One or more messages are processed by a consumer. ||
274
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
275
281
|`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. ||
276
282
|`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. ||
277
283
|`settle`| One or more messages are settled. ||
278
284
285
+
<details>
286
+
<summary><b>Past Defined Values:</b></summary>
287
+
288
+
| Value | Description | Deprecation Explanation |
289
+
|---|---|---|
290
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
291
+
|`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
@@ -136,13 +136,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
136
136
| Value | Description | Stability |
137
137
|---|---|---|
138
138
|`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. ||
139
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
140
139
|`process`| One or more messages are processed by a consumer. ||
141
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
142
140
|`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. ||
143
141
|`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. ||
144
142
|`settle`| One or more messages are settled. ||
145
143
144
+
<details>
145
+
<summary><b>Past Defined Values:</b></summary>
146
+
147
+
| Value | Description | Deprecation Explanation |
148
+
|---|---|---|
149
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
150
+
|`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
@@ -145,13 +145,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
145
145
| Value | Description | Stability |
146
146
|---|---|---|
147
147
|`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. ||
148
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
149
148
|`process`| One or more messages are processed by a consumer. ||
150
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
151
149
|`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. ||
152
150
|`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. ||
153
151
|`settle`| One or more messages are settled. ||
154
152
153
+
<details>
154
+
<summary><b>Past Defined Values:</b></summary>
155
+
156
+
| Value | Description | Deprecation Explanation |
157
+
|---|---|---|
158
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
159
+
|`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
@@ -141,13 +141,21 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
141
141
| Value | Description | Stability |
142
142
|---|---|---|
143
143
|`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. ||
144
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
145
144
|`process`| One or more messages are processed by a consumer. ||
146
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
147
145
|`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. ||
148
146
|`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. ||
149
147
|`settle`| One or more messages are settled. ||
150
148
149
+
<details>
150
+
<summary><b>Past Defined Values:</b></summary>
151
+
152
+
| Value | Description | Deprecation Explanation |
153
+
|---|---|---|
154
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
155
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
156
+
157
+
</details>
158
+
151
159
---
152
160
153
161
`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
@@ -487,13 +487,21 @@ and SHOULD be provided **at span creation time** (if provided at all):
487
487
| Value | Description | Stability |
488
488
|---|---|---|
489
489
|`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. ||
490
-
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
491
490
|`process`| One or more messages are processed by a consumer. ||
492
-
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
493
491
|`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. ||
494
492
|`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. ||
495
493
|`settle`| One or more messages are settled. ||
496
494
495
+
<details>
496
+
<summary><b>Past Defined Values:</b></summary>
497
+
498
+
| Value | Description | Deprecation Explanation |
499
+
|---|---|---|
500
+
|`deliver`| Deprecated. Use `process` instead. | Use `process` instead. |
501
+
|`publish`| Deprecated. Use `send` instead. | Use `send` instead. |
502
+
503
+
</details>
504
+
497
505
---
498
506
499
507
`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