diff --git a/docs/messaging/messaging-spans.md b/docs/messaging/messaging-spans.md index 3d7b8c2b38..3fcaba09d3 100644 --- a/docs/messaging/messaging-spans.md +++ b/docs/messaging/messaging-spans.md @@ -160,17 +160,14 @@ Messaging spans SHOULD follow the overall [guidelines for span names](https://gi The **span name** SHOULD be `{messaging.operation.name} {destination}` (see below for the exact definition of the [`{destination}`](#destination-placeholder) placeholder). -If neither `{messaging.operation.name}` nor `{destination}` are available, span name SHOULD be `{messaging.system}`. - Semantic conventions for individual messaging systems MAY specify different span name format and then MUST document it in [semantic conventions for specific messaging technologies](#semantic-conventions-for-specific-messaging-technologies). The `{destination}` SHOULD describe the entity that the operation is performed against and SHOULD adhere to one of the following values, provided they are accessible: -- `messaging.destination.template` or `messaging.destination.name` SHOULD be used for operations on messages or messaging destinations. - The `messaging.destination.template` SHOULD be used whenever it's available. Otherwise, `messaging.destination.name` SHOULD be used only when - the destination is known to be neither [temporary nor anonymous](#temporary-and-anonymous-destinations). -- `server.address:server.port` SHOULD be used for other operations not targeting any specific destination(s). +1. `messaging.destination.template` SHOULD be used when it is available. +2. `messaging.destination.name` SHOULD be used when the destination is known to be neither [temporary nor anonymous](#temporary-and-anonymous-destinations). +3. `server.address:server.port` SHOULD be used for operations not targeting any specific destination(s). If a corresponding `{destination}` value is not available for a specific operation, the instrumentation SHOULD omit the `{destination}`.