RocketMQ Message Tracing: Concepts, Configuration, and Implementation

Introduction: The article introduces RocketMQ's message tracing feature, which records the full lifecycle of a message across producer, broker, and consumer.

Key attributes recorded include producer instance info, consumer instance info, topic, timestamps, success flags, latency, storage location, key, and tag.

Core benefits: fast problem diagnosis, end‑to‑end link tracking, status monitoring, and audit compliance.

Configuration: Enable tracing by setting traceTopicEnable=true in the broker properties and optionally configure the producer/consumer with setEnableMsgTrace(true) . Two deployment modes are supported – normal mode (tracing data shares broker nodes) and physical I/O isolation mode (dedicated broker for tracing).

Implementation principle: RocketMQ creates an internal topic RMQ_SYS_TRACE_TOPIC to store trace data. Hooks on producer and consumer generate trace records and send them to this topic, which can be queried via console or API.

Topic support: Users can use the default trace topic or define a custom trace topic (e.g., MyApp_TraceTopic ) for special storage or security requirements.

Code examples: The article provides Java snippets for a producer and a consumer that enable tracing and specify a custom trace topic, as well as commands to create the custom topic and query trace data.