Diagnosing a RocketMQ Instance

Prerequisites

• A consumer group has been created, and there are consumers in the group.
• A topic has been created.

Procedure

1. Log in to the RocketMQ console.
2. Click a RocketMQ instance name to go to the instance overview page.
3. In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
4. Select a consumer group and click Start Diagnose.

   After the diagnosis is complete, a diagnosis record is displayed in the Diagnosis Reports area.

5. Click View to go to the Diagnosis Report to view the diagnosis result.

   The result contains the active status, number of consumers, subscription consistency, client ID, consumption type, and message accumulation.

   Figure 1 Diagnosis result
   
   

   If the consumer group is not online, the diagnosis is successful, but one abnormality is displayed.

6. (Optional) In the Consumer Connections area, click View in the Operation column to view the diagnosis details.
   Figure 2 Diagnosis details
   

Exporting Diagnosis Records

1. Log in to the RocketMQ console.
2. Click a RocketMQ instance name to go to the instance overview page.
3. In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
4. Export instance diagnosis records in either of the following ways:
   • Select the desired records and choose Export > Export selected data to an XLSX file.
   • Choose Export > Export all data to an XLSX file to export all the records.

Deleting Diagnosis Records

1. Log in to the RocketMQ console.
2. Click a RocketMQ instance name to go to the instance overview page.
3. In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
4. Use either of the following methods to delete diagnosis records:
   • In the row containing the record you want to delete, click Delete.
   • Select multiple records you want to delete and click Delete above the record list.

5. In the confirmation dialog box, click OK.

Related Documents

• To handle message accumulation excess, see Handling Message Accumulation.
• To handle subscription inconsistency, see Ensuring Subscription Consistency.