Semantic Conventions for RocketMQ

Status: Experimental

The Semantic Conventions for Apache RocketMQ extend and override the Messaging Semantic Conventions.

messaging.system MUST be set to "rocketmq" and SHOULD be provided at span creation time.

Apache RocketMQ attributes

Specific attributes for Apache RocketMQ are defined below.

Attribute	Type	Description	Examples	Requirement Level	Stability
messaging.consumer.group.name	string	RocketMQ consumer group name.	my-group; indexer	Required
messaging.operation.name	string	The system-specific name of the messaging operation.	ack; nack; send	Required
messaging.rocketmq.namespace	string	Namespace of RocketMQ resources, resources in different namespaces are individual.	myNamespace	Required
error.type	string	Describes a class of error the operation ended with. [1]	amqp:decode-error; KAFKA_STORAGE_ERROR; channel-error	Conditionally Required If and only if the messaging operation has failed.
messaging.batch.message_count	int	The number of messages sent, received, or processed in the scope of the batching operation. [2]	0; 1; 2	Conditionally Required [3]
messaging.destination.name	string	The message destination name [4]	MyQueue; MyTopic	Conditionally Required [5]
messaging.operation.type	string	A string identifying the type of the messaging operation. [6]	publish; create; receive	Conditionally Required If applicable.
messaging.rocketmq.message.delay_time_level	int	The delay time level for delay message, which determines the message delay time.	3	Conditionally Required [7]
messaging.rocketmq.message.delivery_timestamp	int	The timestamp in milliseconds that the delay message is expected to be delivered to consumer.	1665987217045	Conditionally Required [8]
messaging.rocketmq.message.group	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.	myMessageGroup	Conditionally Required If the message type is FIFO.
server.address	string	Server domain name if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name. [9]	example.com; 10.1.2.80; /tmp/my.sock	Conditionally Required If available.
messaging.client.id	string	A unique identifier for the client that consumes or produces a message.	client-5; myhost@8742@s8083jm	Recommended
messaging.message.body.size	int	The size of the message body in bytes. [10]	1439	Recommended
messaging.message.id	string	A value used by the messaging system as an identifier for the message, represented as a string.	452a7c7c7c7048c2f887f61572b18fc2	Recommended If span describes operation on a single message.
messaging.rocketmq.consumption_model	string	Model of message consumption. This only applies to consumer spans.	clustering; broadcasting	Recommended
messaging.rocketmq.message.keys	string[]	Key(s) of message, another way to mark message besides message id.	["keyA", "keyB"]	Recommended
messaging.rocketmq.message.tag	string	The secondary classifier of message besides topic.	tagA	Recommended
messaging.rocketmq.message.type	string	Type of message.	normal; fifo; delay	Recommended
server.port	int	Server port number. [11]	80; 8080; 443	Recommended

[1]: The error.type SHOULD be predictable, and SHOULD have low cardinality.

When error.type is set to a type (e.g., an exception type), its canonical class name identifying the type within the artifact SHOULD be used.

Instrumentations SHOULD document the list of errors they report.

The cardinality of error.type within one instrumentation library SHOULD be low. Telemetry consumers that aggregate data from multiple instrumentation libraries and applications should be prepared for error.type to have high cardinality at query time when no additional filters are applied.

If the operation has completed successfully, instrumentations SHOULD NOT set error.type.

If a specific domain defines its own set of error identifiers (such as HTTP or gRPC status codes), it’s RECOMMENDED to:

• Use a domain-specific attribute
• Set error.type to capture all errors, regardless of whether they are defined within the domain-specific set or not.

[2]: 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.

[3]: If the span describes an operation on a batch of messages.

[4]: 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.

[5]: If span describes operation on a single message or if the value applies to all messages in the batch.

[6]: If a custom value is used, it MUST be of low cardinality.

[7]: If the message type is delay and delivery timestamp is not specified.

[8]: If the message type is delay and delay time level is not specified.

[9]: Server domain name of the broker if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name.

[10]: This can refer to both the compressed or uncompressed body size. If both sizes are known, the uncompressed body size should be used.

[11]: When observed from the client side, and when communicating through an intermediary, server.port SHOULD represent the server port behind any intermediaries, for example proxies, if it’s available.

The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):

• messaging.consumer.group.name
• messaging.destination.name
• messaging.operation.name
• messaging.operation.type
• server.address
• server.port

error.type 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.

Value	Description	Stability
_OTHER	A fallback error value to be used when the instrumentation doesn’t define a custom value.

messaging.operation.type 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.

Value	Description	Stability
create	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.
process	One or more messages are processed by a consumer.
publish	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.
receive	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.
settle	One or more messages are settled.

messaging.rocketmq.consumption_model 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.

Value	Description	Stability
broadcasting	Broadcasting consumption model
clustering	Clustering consumption model

messaging.rocketmq.message.type 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.

Value	Description	Stability
delay	Delay message
fifo	FIFO message
normal	Normal message
transaction	Transaction message

messaging.client.id SHOULD be set to the client ID that is automatically generated by the Apache RocketMQ SDK.