Message queue RabbitMQ meets observable--business link visualization

Author: Wen Ting, Bu Zhou

This article mainly introduces the observable function of Alibaba Cloud Message Queue RabbitMQ version. Compared with open source, the observability of RabbitMQ has been comprehensively strengthened to escort business links.

Introduction to message queue RabbitMQ

Alibaba Cloud Message Queue RabbitMQ version is a message product based on the AMQP 0-9-1 protocol implemented by a high-availability distributed storage architecture. It is compatible with the open source RabbitMQ client and solves various stability pain points of open source (such as message accumulation, split-brain, etc. problem), and has the advantages of cloud messaging services such as high concurrency, distribution, and flexible expansion and contraction.

The observability of Alibaba Cloud's message queue RabbitMQ has been comprehensively enhanced compared to open source. So in what scenarios can the observability be used?

Why Strong Observability Capabilities Are Needed

With the rise of distributed and cloud-native architectures, system observability plays an increasingly important role in troubleshooting, system operation and maintenance, and even business operations.

Scenario 1: There is an abnormality in online message consumption, and the message cannot be processed in time. It is necessary to receive an alarm in time and quickly locate the problem;

Scenario 2: The status of some online orders is abnormal, and it is necessary to check whether the corresponding message link is sending messages normally;

Scenario 3: It is necessary to analyze the change trend of message traffic, traffic distribution characteristics or message volume, and then conduct business trend analysis and planning;

Scenario 4: It is necessary to view and analyze the upstream and downstream dependency topology of the application, and perform architecture upgrade optimization or transformation.

Message queue RabbitMQ observability

Combined with the above content, the following introduces the two core functions of the observability of Alibaba Cloud message queue RabbitMQ.

core advantages

• Observable Dashboard market

1. Optimized performance, with super stability;

2. One-click unpacking to reduce construction costs;

3. The presentation is clear, and the problem resources are visible at a glance.

• Observable message trace **

1. Ability to screen and search for various problem scenarios;

2. It supports graphical display of complex trajectory information, making it more convenient to use.

Observable Dashboard market

• Application scenarios

Using the Prometheus monitoring service and Grafana's indicator storage and display capabilities, the RabbitMQ version of the message queue provides the Dashboard function for Enterprise and Platinum instances. With this feature, you can view various metrics of instances, Vhosts, Queues, and Exchanges to help you discover and locate problems in time.

• Features

1. Multi-dimensional combined query capability: You can aggregate and query data from cluster, Vhost, Exchange, and Queue in multiple dimensions;

2. Sorting ability: Under the same indicator, the resources are sorted in reverse order according to their health status, and the most problematic resources in the cluster can be seen at a glance;

3. Rich indicator data: message volume, connection number, accumulation volume, key interface request data, etc.

Observable message trace

• Application scenarios

If the message sending and receiving does not meet expectations, you can quickly analyze the historical message sending and receiving details and locate the cause of the problem by querying the message track, so as to restore the business in time.

• Features

1. Inquiry ability

• Query by Queue: Query the traces of all messages on the Queue within a certain time range. It is suitable for fuzzy query scenarios where you only know the Queue to which the message is sent, but do not know the Message ID set when sending the message.
• Query by Message ID: Specify the message according to the exact query of Message ID. Message ID is set to a unique ID related to the business.
• Processing time by message: Query the message trace according to the message processing time (the time from when the message is delivered to the consumer to when the consumer finishes processing and returns a response) greater than the specified time.

2. Track content

• View the time of each stage of the life cycle: message arrival time, delivery time, response time, dead letter entry time, etc.;
• View the message flow link information: the link topology information of the message from the producer to the Exchange to the Queue to the consumer;
• View producer and consumer information: IP address, account ID;
• View failure reasons: sending failure, consumption failure reasons, dead letter reasons, etc.

Click here to enter the official website for more details~