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
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,7 +142,9 @@ 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`. |
145
146
|`process`| One or more messages are processed by a consumer. ||
147
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
146
148
|`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. ||
147
149
|`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. ||
148
150
|`settle`| One or more messages are settled. ||
@@ -267,7 +269,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
267
269
| Value | Description | Stability |
268
270
|---|---|---|
269
271
|`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`. |
270
273
|`process`| One or more messages are processed by a consumer. ||
274
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
271
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. ||
272
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. ||
273
277
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/gcp-pubsub.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,7 +136,9 @@ 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`. |
139
140
|`process`| One or more messages are processed by a consumer. ||
141
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
140
142
|`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
143
|`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
144
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/kafka.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,9 @@ 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`. |
148
149
|`process`| One or more messages are processed by a consumer. ||
150
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
149
151
|`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
152
|`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
153
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/messaging-metrics.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,9 @@ 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`. |
144
145
|`process`| One or more messages are processed by a consumer. ||
146
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
145
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. ||
146
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. ||
147
149
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/messaging-spans.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -487,7 +487,9 @@ 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`. |
490
491
|`process`| One or more messages are processed by a consumer. ||
492
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
491
493
|`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
494
|`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
495
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/rabbitmq.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
133
133
| Value | Description | Stability |
134
134
|---|---|---|
135
135
|`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. ||
136
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
136
137
|`process`| One or more messages are processed by a consumer. ||
138
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
137
139
|`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. ||
138
140
|`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. ||
139
141
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/rocketmq.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
140
140
| Value | Description | Stability |
141
141
|---|---|---|
142
142
|`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. ||
143
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
143
144
|`process`| One or more messages are processed by a consumer. ||
145
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
144
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. ||
145
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. ||
146
148
|`settle`| One or more messages are settled. ||
Copy file name to clipboardExpand all lines: docs/messaging/sns.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
87
87
| Value | Description | Stability |
88
88
|---|---|---|
89
89
|`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. ||
90
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
90
91
|`process`| One or more messages are processed by a consumer. ||
92
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
91
93
|`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. ||
92
94
|`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. ||
93
95
|`settle`| One or more messages are settled. ||
0 commit comments