messaging.destination.name
Developmentstringas of v1.44.0
The message destination name
SHOULD uniquely identify a specific queue, topic or other entity within the broker. If the broker doesn't have such notion, it SHOULD uniquely identify the broker.
Examples
- MyQueue
- MyTopic
Used by
spans (45)
- messaging.create.producer
- messaging.create.producer
- messaging.eventhubs.generic.client
- messaging.eventhubs.generic.client
- messaging.process.consumer
- messaging.process.consumer
- messaging.receive.client
- messaging.receive.client
- messaging.send.client
- messaging.send.client
- messaging.send.producer
- messaging.send.producer
- messaging.servicebus.generic.client
- messaging.servicebus.generic.client
- messaging.settle.client
- messaging.settle.client
- messaging.send.producer
- messaging.process.consumer
- messaging.receive.client
- messaging.send.producer
- messaging.create.producer
- messaging.process.consumer
- messaging.receive.client
- messaging.send.client
- messaging.send.producer
- messaging.settle.client
- messaging.create.producer
- messaging.process.consumer
- messaging.receive.client
- messaging.send.client
- messaging.send.producer
- messaging.settle.client
- messaging.create.producer
- messaging.process.consumer
- messaging.receive.client
- messaging.send.client
- messaging.send.producer
- messaging.settle.client
- messaging.process.consumer *
- messaging.receive.client *
- and 5 more
metrics (5)
- messaging.client.consumed.messages
- messaging.client.operation.duration
- messaging.client.published.messages
- messaging.client.sent.messages
- 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).