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
@@ -139,7 +139,9 @@ 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`. |
142
143
|`process`| One or more messages are processed by a consumer. ||
144
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
143
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. ||
144
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. ||
145
147
|`settle`| One or more messages are settled. ||
@@ -261,7 +263,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
261
263
| Value | Description | Stability |
262
264
|---|---|---|
263
265
|`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`. |
264
267
|`process`| One or more messages are processed by a consumer. ||
268
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
265
269
|`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. ||
266
270
|`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. ||
267
271
|`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
@@ -134,7 +134,9 @@ 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`. |
137
138
|`process`| One or more messages are processed by a consumer. ||
139
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
138
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. ||
139
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. ||
140
142
|`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
@@ -143,7 +143,9 @@ 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`. |
146
147
|`process`| One or more messages are processed by a consumer. ||
148
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
147
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. ||
148
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. ||
149
151
|`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
@@ -139,7 +139,9 @@ 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`. |
142
143
|`process`| One or more messages are processed by a consumer. ||
144
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
143
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. ||
144
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. ||
145
147
|`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
@@ -485,7 +485,9 @@ 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`. |
488
489
|`process`| One or more messages are processed by a consumer. ||
490
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
489
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. ||
490
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. ||
491
493
|`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
@@ -131,7 +131,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
131
131
| Value | Description | Stability |
132
132
|---|---|---|
133
133
|`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. ||
134
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
134
135
|`process`| One or more messages are processed by a consumer. ||
136
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
135
137
|`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. ||
136
138
|`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. ||
137
139
|`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
@@ -138,7 +138,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
138
138
| Value | Description | Stability |
139
139
|---|---|---|
140
140
|`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. ||
141
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
141
142
|`process`| One or more messages are processed by a consumer. ||
143
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
142
144
|`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
145
|`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
146
|`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
@@ -85,7 +85,9 @@ and SHOULD be provided **at span creation time** (if provided at all):
85
85
| Value | Description | Stability |
86
86
|---|---|---|
87
87
|`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. ||
88
+
|`deliver`| Deprecated. Use `process` instead. |<br>Replaced by `process`. |
88
89
|`process`| One or more messages are processed by a consumer. ||
90
+
|`publish`| Deprecated. Use `send` instead. |<br>Replaced by `send`. |
89
91
|`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. ||
90
92
|`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. ||
91
93
|`settle`| One or more messages are settled. ||
0 commit comments