ApsaraMQ for RocketMQ is a distributed messaging middleware that is widely used in the core systems of business. Each message in ApsaraMQ forRocketMQ reflects changes in core business data. To ensure business running, it is important to identify, locate, and troubleshoot issues by using the observability feature. This topic describes the major features of observability in ApsaraMQ for RocketMQ.
The observability system of ApsaraMQ for RocketMQ consists of metrics, message traces, and logs.
The metrics defined in ApsaraMQ for RocketMQ cover statistics that are related to producers, consumers, brokers, and key operations and procedures for messaging. You can view the metrics by instance, topic, and group. The metrics help you monitor the running status of your business or ApsaraMQ for RocketMQ in real time.
In addition to the metrics included in ApsaraMQ for RocketMQ 4.x brokers, Message Queue for Apache 5.x brokers also provide metrics related to message accumulation, time consumed for key operations, error distribution, and read and write traffic for storage. This helps you monitor exceptions.
ApsaraMQ for RocketMQ is a critical service for asynchronous decoupling in distributed applications. The tracing data that is provided by ApsaraMQ forRocketMQ effectively connects the upstream and downstream systems of the business. This helps you troubleshoot exceptions and locate issues.
Compared with ApsaraMQ for RocketMQ 4.x brokers, ApsaraMQ forRocketMQ 5.x brokers support the OpenTelemetry protocol, provide more tracing metrics, and refine the trace content for scenarios such as message consumption and advanced message types. This helps provide more critical information for troubleshooting.
Each exception that occurs in ApsaraMQ for RocketMQ is assigned a unique error code and error message. Errors are divided into different levels. You can quickly determine the cause of an exception based on the error code and error message that are returned by the client.
In ApsaraMQ for RocketMQ5.x brokers, the error code and error message of an exception are combined. The request ID and resource information are also added to exception logs to ensure the clarity and reliability of the logs.