Skip to content

Commit c36fed7

Browse files
committed
Add settle spans from OTEP 220
1 parent c9252a1 commit c36fed7

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/messaging/messaging-spans.md

+7
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,7 @@ The following operations related to messages are defined for these semantic conv
206206
| `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. |
207207
| `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. |
208208
| `deliver` | One or more messages are passed to a consumer. This operation refers to push-based scenarios, where consumer register callbacks which get called by messaging SDKs. |
209+
| `settle` | One or more messages are settled. |
209210

210211
### Span kind
211212

@@ -269,6 +270,12 @@ batch of messages, or for no message at all (if it is signalled that no
269270
messages were received). For each message it accounts for, the "Deliver" or
270271
"Receive" span SHOULD link to the message's creation context.
271272

273+
"Settle" spans SHOULD be created for every manually or automatically triggered
274+
settlement operation. A single "Settle" span can account for a single message
275+
or for multiple messages (in case messages are passed for settling as batches).
276+
For each message it accounts for, the "Settle" span MAY link to the creation
277+
context of the message.
278+
272279
## Messaging attributes
273280

274281
Messaging attributes are organized into the following namespaces:

0 commit comments

Comments
 (0)