When applications exchange messages through Message Queue for Apache RocketMQ, failed publishes, slow consumers, or broken topic connections can disrupt your entire service chain. MQ monitoring provides visibility into message publishing and subscription for your EDAS applications, so you can detect issues before they cascade into downstream failures.
With MQ monitoring, you can:
Visualize publishing and subscription relationships between your application and RocketMQ topics.
Track request volume, response time, and error rates for both publishers and subscribers.
Trace individual message requests to pinpoint the exact step that introduced latency or errors.
Supported editions
MQ monitoring requires Professional Edition or Platinum Edition. Standard Edition does not support this feature.
Open the MQ monitoring page
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace.
From the Cluster Type drop-down list, select Kubernetes Cluster.
Find the target application and click its name in the Application Name column.
In the left-side navigation pane of the application details page, choose Monitor > MQ Monitoring.
Understand topic relationships
The Overview tab displays a topology map of the message publishing and subscription relationships between your EDAS application and its RocketMQ topics.
Use this view to:
Verify that your application connects to the expected topics.
Spot missing or unexpected connections that may indicate misconfiguration.
Assess the overall health of your messaging architecture at a glance.
Monitor publishing performance
The Publishing Statistics tab tracks metrics for messages your application publishes to RocketMQ topics.
| Metric | Description |
|---|---|
| Request count | Total number of publish requests sent to RocketMQ |
| Response time (RT) | Time taken for each publish request to complete |
| Error count | Number of failed publish requests |
Monitor subscription performance
The Subscription Statistics tab tracks metrics for messages your application consumes from RocketMQ topics.
| Metric | Description |
|---|---|
| Request count | Total number of subscription requests processed |
| Response time (RT) | Time taken for each subscription request to complete |
| Error count | Number of failed subscription requests |
Trace individual message requests
The Interface Snapshot tab lists individual API calls for both message publishing and subscription. Each entry includes a TraceId value. Click a TraceId to view the trace information and diagnose issues.
Use interface snapshots to:
Diagnose specific failed or slow message operations.
Identify which step in the request chain introduced latency or errors.