-
As we know, the RocketMQ 4.x use message trace as observability. With RocketMQ 5.x, it use opentelemetry metric. But for some scenarios, we have no a professional ops team, we just need the traditional and simple trace on rocketmq-dashboard. In Aliyun ons TCP client, they implement a message trace interceptor to wrap the traceContext as part of the Message systemProperties. /cc @aaron-ai |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
In the future, we plan to make the interceptor hook available for users to replace the 'message trace' counterpart in RocketMQ 4.x. However, 'message trace' in 4.x is not available in 5.x as it is not part of our current roadmap. As a solution, we use OpenTelemetry as our observability tool for tracing and metrics, which is a universal and versatile solution suitable for distributed messaging systems. You may refer to the related documentation for further information. |
Beta Was this translation helpful? Give feedback.
In the future, we plan to make the interceptor hook available for users to replace the 'message trace' counterpart in RocketMQ 4.x. However, 'message trace' in 4.x is not available in 5.x as it is not part of our current roadmap.
As a solution, we use OpenTelemetry as our observability tool for tracing and metrics, which is a universal and versatile solution suitable for distributed messaging systems. You may refer to the related documentation for further information.