From 18c532f1a77e3bf90af2bd1c106c6a80bb8c01c1 Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Fri, 23 Feb 2024 14:53:47 -0800 Subject: [PATCH] up --- docs/messaging/azure-messaging.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/messaging/azure-messaging.md b/docs/messaging/azure-messaging.md index 47f1576fd0..5966bab135 100644 --- a/docs/messaging/azure-messaging.md +++ b/docs/messaging/azure-messaging.md @@ -16,10 +16,9 @@ The Semantic Conventions for [Azure Service Bus](https://learn.microsoft.com/azu The span name SHOULD follow [general messaging span name pattern](../messaging/azure-messaging.md): it SHOULD start with the messaging destination name (Event Hubs queue or topic name) and contain a low-cardinality name of an operation span describes: - -- Spans for `deliver` operation SHOULD follow ` process` pattern (matching terminology used in Azure client libraries) -- Spans for `settle` operation SHOULD follow ` ` pattern. Disposition status MUST match the value of `messaging.servicebus.disposition_status` attribute. +- Spans names for `settle` operation SHOULD follow ` {messaging.servicebus.disposition_status}` pattern. For example, `my-queue complete` or `my-queue abandon` +- Spans names for `publish` operation SHOULD follow ` send` pattern. - Spans for `create`, `receive`, and `publish` operations SHOULD follow general ` ` pattern ### Span attributes @@ -45,8 +44,8 @@ The following additional attributes are defined: The span name SHOULD follow [general messaging span name pattern](../messaging/azure-messaging.md): it SHOULD start with the messaging destination name (Event Hubs namespace) and contain a low-cardinality name of an operation span describes: -- Spans for `deliver` operation SHOULD follow ` process` pattern (matching terminology used in Azure client libraries) - Spans for `settle` operation SHOULD follow ` checkpoint` (matching Event Hubs terminology) +- Spans names for `publish` operation SHOULD follow ` send` pattern - Spans for `create`, `receive`, and `publish` operations SHOULD follow general ` ` pattern ### Span attributes