- Host:
net.peer.name:net.peer.port
(actual host contacted)- always present
- Topic name:
messaging.destination.name
- maybe present per message, not per publish call - https://stackoverflow.com/questions/39093488/can-single-kafka-producer-produce-messages-to-multiple-topics-and-how
no url notion
- Host:
net.peer.name:net.peer.port
- maybe present
- queue or topic name:
messaging.destination.name
- always present
- Host:
net.peer.name:net.peer.port
- always present
- Exchange:
messaging.destination.name
- always present
- Routing key: TBD
- Host:
net.peer.name:net.peer.port
(actual server contacted)- always present
- Subject
messaging.destination.name
- always present
- Host:
net.peer.name:net.peer.port
- always present
- Topic:
messaging.destination.name
- full path tenant/namespace/topic: client doesn't really know - https://github.com/streamnative/examples/blob/master/clients/pubsub/examples/dead-letter-topic.md- always present
- Host:
net.peer.name:net.peer.port
- always present
- Topic:
messaging.destination.name
- always present, per batch
- Region:
cloud.region
- always present
- Account number:
cloud.account.id
- always present
- Queue name:
messaging.destination.name
- always present
AWS lambda samples for queues: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/instrumentation/aws-lambda.md
- Region:
cloud.region
- always present
- Account number:
cloud.account.id
- always present
- Topic name:
messaging.destination.name
- always present
- Region:
cloud.region
- always present
- Account number:
cloud.account.id
- always present
- Stream name:
messaging.destination.name
- always present
- Host (aka namespace):
net.peer.name:net.peer.port
-test.servicebus.windows.net
- always present
- Event Hub topic:
messaging.destination.name
- always present
- Host (aka namespace):
net.peer.name:net.peer.port
-test.servicebus.windows.net
- always present
- Topic or queue:
messaging.destination.name
- always present
- Host (aka namespace):
net.peer.name:net.peer.port
-test.eventgrid.azure.net
- always present
- Topic or queue:
messaging.destination.name
- available sometimes (for domains) and on per-message level- maybe present
- Project id -
cloud.account.id
- always present
- Topic:
messaging.destination.name
- always present
no url notion
- Host:
net.peer.name:net.peer.port
, e.g.amqp://guest:guest@localhost:5672
- Node name
messaging.destination.name
- Host:
net.peer.name:net.peer.port
, e. g.localhost:5555
- Topic name
messaging.destination.name