GitHub user aaron-ai added a comment to the discussion: What not implement the traceContext in Clients?
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. * [Trace for Messaging System](https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/messaging/) * [RocketMQ 5.0 Tracing Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/rocketmq/rocketmq-client/rocketmq-client-5.0) * [Kafka Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/kafka) * [RabbitMQ Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/rabbitmq-2.7) GitHub link: https://github.com/apache/rocketmq-clients/discussions/474#discussioncomment-5611756 ---- This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
