ApsaraMQ for RabbitMQ:Logs

Billing

• ApsaraMQ for RabbitMQ

  You are not charged for using the message log management feature.

• Simple Log Service

  After ApsaraMQ for RabbitMQ pushes logs to Simple Log Service, you are charged for items like storage, traffic, and requests. For more information, see Billable items of pay-as-you-go.

Log format

Procedure

To push logs from your ApsaraMQ for RabbitMQ instance to Simple Log Service, configure a destination.

1. Log on to the ApsaraMQ for RabbitMQ console. In the left-side navigation pane, click Instances.

2. In the top navigation bar of the Instances page, select the region where the instance that you want to manage resides. Then, in the instance list, click the name of the instance that you want to manage.

3. In the left-side navigation pane, click Log Management.

4. On the My Resources card, click Authorize Now.

   If you have already granted ApsaraMQ for RabbitMQ the permissions to access Simple Log Service, skip this step.

5. On the Log Management page, select the project and Logstore that you created from the Project Name and Logstore drop-down lists, and then click Enable.

6. Log on to the Simple Log Service console. Enable and configure field indexes for your logs. For more information, see Create indexes.

7. Manually add the __tag__:__receive_time__ field and set its alias to timestamp.

Tutorials

• Common queries for troubleshooting

• How to generate second-level metrics

• Count message send/receive operations by queue to identify high-cost queues

  When the ApsaraMQ for RabbitMQ console does not provide queue-level billing breakdowns, you can use the operation logs in Simple Log Service to independently count message operations by queue and locate high-consumption queues, without relying on backend data extraction.

  In Simple Log Service, query the operation logs of your ApsaraMQ for RabbitMQ instance and run the following query statement to aggregate the number of SendMessage, PushMessage, and BasicGet operations per queue within a specified time range, sorted by operation count in descending order:

  Action: SendMessage OR Action: PushMessage OR Action: BasicGet | SELECT Queue, Action, COUNT(*) AS operation_count GROUP BY Queue, Action ORDER BY operation_count DESC LIMIT 100

  Action	Description
  SendMessage	A producer sends a message to ApsaraMQ for RabbitMQ.
  PushMessage	The broker pushes a message to a consumer.
  BasicGet	A consumer client pulls a message.

  The results show which queues have the highest message throughput. Use these results to pinpoint the source of high costs and prioritize optimization without waiting for backend data extraction.

FAQ

Q: Why is there a time difference between the client log timestamp and the server delivery success time in ApsaraMQ for RabbitMQ?

A: To troubleshoot this discrepancy, follow these steps:

1. Check server-side logs first. Query the operation logs in Simple Log Service to verify that the server delivered the message successfully and without delay. Filter by Action: PushMessage OR Action: DeleteMessage and confirm that the Code field value is 200. If the server-side logs are normal, the server is not the cause of the time difference.

2. Investigate the client environment. If the server-side logs show no issues, the discrepancy is typically caused by the client side. Check for the following conditions:

   • Network latency or packet loss: Intermittent network issues between the client and the ApsaraMQ for RabbitMQ service can delay message acknowledgment on the client side.

   • High CPU usage: A heavily loaded CPU can delay the execution of message-sending methods (for example, convertAndSend), causing the client-recorded timestamp to lag behind the server's actual delivery time.

   • Frequent Full GC pauses: JVM Full GC events pause all application threads, which can significantly increase the time between invoking a send method and actual message delivery. This causes the client log to record a later timestamp than the server's delivery time.

Q: How do I analyze the cause of an issue after receiving an alarm log or alert notification from ApsaraMQ for RabbitMQ?

A: When you receive an alarm log or alert notification, follow these steps to identify the root cause:

1. Locate the console link in the alarm log. Alarm logs include a URL that directs you to the relevant monitoring or management page in the cloud console. Find this URL in the alarm log content.

2. Open the Task Details page. Click the URL in the alarm log to access the Task Details page or the cluster monitoring page directly. This page provides the alarm context, associated metrics, and event timeline to help you diagnose the underlying issue.

3. Correlate with operation logs. Cross-reference the alarm event timestamp with the operation logs in Simple Log Service to identify correlated message operations (such as connection failures, message rejections, or dead-letter routing) that occurred at the same time and may have contributed to the alarm.