|int||The number of messages sent, received, or processed in the scope of the batching operation. |
|string||A unique identifier for the client that consumes or produces a message.|
|boolean||A boolean that is true if the message destination is anonymous (could be unnamed or have auto-generated name).|
|string||The message destination name |
|string||Low cardinality representation of the messaging destination name |
|boolean||A boolean that is true if the message destination is temporary and might not exist anymore after messages are processed.|
|boolean||A boolean that is true if the publish message destination is anonymous (could be unnamed or have auto-generated name).|
|string||The name of the original destination the message was published to |
|string||Name of the Kafka Consumer Group that is handling the message. Only applies to consumers, not producers.|
|int||Partition the message is sent to.|
|string||Message keys in Kafka are used for grouping alike messages to ensure they’re processed on the same partition. They differ from |
|int||The offset of a record in the corresponding Kafka partition.|
|boolean||A boolean that is true if the message is a tombstone.|
|int||The size of the message body in bytes. |
|string||The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called “Correlation ID”.|
|int||The size of the message body and metadata in bytes. |
|string||A value used by the messaging system as an identifier for the message, represented as a string.|
|string||A string identifying the kind of messaging operation. |
|string||RabbitMQ message routing key.|
|string||Name of the RocketMQ producer/consumer group that is handling the message. The client type is identified by the SpanKind.|
|string||Model of message consumption. This only applies to consumer spans.|
|int||The delay time level for delay message, which determines the message delay time.|
|int||The timestamp in milliseconds that the delay message is expected to be delivered to consumer.|
|string||It is essential for FIFO message. Messages that belong to the same message group are always processed one by one within the same consumer group.|
|string||Key(s) of message, another way to mark message besides message id.|
|string||The secondary classifier of message besides topic.|
|string||Type of message.|
|string||Namespace of RocketMQ resources, resources in different namespaces are individual.|
|string||A string identifying the messaging system.|
: Instrumentations SHOULD NOT set
messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use
messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.
: Destination name SHOULD uniquely identify a specific queue, topic or other entity within the broker. If the broker doesn’t have such notion, the destination name SHOULD uniquely identify the broker.
: Destination names could be constructed from templates. An example would be a destination name involving a user name or product id. Although the destination name in this case is of high cardinality, the underlying template is of low cardinality and can be effectively used for grouping and aggregation.
: The name SHOULD uniquely identify a specific queue, topic, or other entity within the broker. If the broker doesn’t have such notion, the original destination name SHOULD uniquely identify the broker.
: If the key type is not string, it’s string representation has to be supplied for the attribute. If the key has no unambiguous, canonical string form, don’t include its value.
: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed body size should be used.
: This can refer to both the compressed or uncompressed size. If both sizes are known, the uncompressed size should be used.
: If a custom value is used, it MUST be of low cardinality.
messaging.operation has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.
|One or more messages are provided for publishing to an intermediary. If a single message is published, the context of the “Publish” span can be used as the creation context and no “Create” span needs to be created.|
|A message is created. “Create” spans always refer to a single message and are used to provide a unique creation context for messages in batch publishing scenarios.|
|One or more messages are requested by a consumer. This operation refers to pull-based scenarios, where consumers explicitly call methods of messaging SDKs to receive messages.|
|One or more messages are passed to a consumer. This operation refers to push-based scenarios, where consumer register callbacks which get called by messaging SDKs.|
messaging.rocketmq.consumption_model MUST be one of the following:
|Clustering consumption model|
|Broadcasting consumption model|
messaging.rocketmq.message.type MUST be one of the following: