messaging.destination.subscription.name
Developmentstringas of v1.44.0
The name of the destination subscription from which a message is consumed.
Semantic conventions for individual messaging systems SHOULD document whether messaging.destination.subscription.name is applicable and what it means in the context of that system.
Examples
- subscription-a
Used by
spans (7)
- messaging.servicebus.generic.client
- messaging.process.consumer
- messaging.receive.client
- messaging.settle.client
- messaging.process.consumer
- messaging.receive.client
- messaging.settle.client
metrics (3)
- messaging.client.consumed.messages
- messaging.client.operation.duration
- messaging.process.duration
* required on that signal.
History
Stability label respelled from experimental to development.
Already present at v1.30.0, the oldest release tracked here (experimental).