-
What do the metrics on the ApsaraMQ for RocketMQ dashboard mean?
-
Why can't I view instances, topics, and groups in the console?
-
Why can't I query the trace of a delayed message in the console?
-
Are the permission policies for 5.0 series instances and 4.0 series instances the same?
-
What is the difference between average TPS and maximum TPS on the dashboard?
Dashboard metrics
-
For 5.0 series instances, see Dashboard for 5.0 series instances.
-
For 4.0 series instances, see Dashboard for 4.0 series instances.
Message trace for consumption verification
The consumption verification feature uses management APIs to check if a message can be consumed. This process is independent of the standard message flow and does not generate a message trace.
View resources in the console
If you are logged in as a RAM user, ensure your account has the required permissions to access ApsaraMQ for RocketMQ resources.
-
For 5.0 series instances, see Permission policies and examples for 5.0 series instances.
-
For 4.0 series instances, see Permission policies and examples for 4.0 series instances.
Query trace for delayed messages
You can query the message trace of a scheduled/delayed message only after its scheduled delivery time has passed.
View resource operation records
Follow these steps to view operation records in the ActionTrail console:
-
Log on to the ActionTrail console. In the navigation pane on the left, click Event Query.
-
In the top navigation bar, select the region where the resource is located.
-
On the Event Query page, select Resource Name from the filter drop-down list. In the search box, enter the name of the resource, such as an instance ID, topic name, or group ID. For example, you can enter
mq_topic. Specify a time range and click the search icon. The results list displays the related operation events, including the event time, operator, cloud service, event name, and related resources.
Grant full instance permissions
-
For 5.0 series instances, see Permission policy examples for 5.0 series instances.
-
For 4.0 series instances, see Permission policy examples for 4.0 series instances.
How do I release and delete an instance?
Instance type | Unsubscription method | Procedure |
5.x series instance | Self-service unsubscription | On the Unsubscriptions page in the Expenses and Costs console, select Partial Unsubscription, find the Message Queue for Apache RocketMQ instance that you want to unsubscribe, click Unsubscribe Resource in the Actions column, and follow the prompts to complete the unsubscription. |
4.x series instance (Enterprise Platinum Edition) | Self-service unsubscription | |
4.x series instance (Standard Edition) | No unsubscription is involved. Release the resource directly. | In the ApsaraMQ for RocketMQ console, delete all topics and groups in the instance. Then, on the Instance Details page, click Delete Instance. |
Permission policies for 5.0 and 4.0 series instances
No. The 5.0 and 4.0 series instances use different permission policies that are managed separately. You must use the policies that match the instance's series.
-
For 5.0 series instances, see Permission policy examples for 5.0 series instances.
-
For 4.0 series instances, see Permission policy examples for 4.0 series instances.
Average TPS vs. maximum TPS
average TPS = Total number of requests in a 1-minute period / 60 seconds
maximum TPS: The system samples the TPS value once per second over a 1-minute period. The maximum TPS is the highest value among the 60 samples.
For example:
Assume an instance produces 60 messages in one minute (all are normal messages of 4 KB each).
average TPS of the instance = 60 requests / 60 seconds = 1 request/second
The maximum TPS of the instance is calculated as follows:
If all 60 messages are sent within the first second, the TPS for each second of that minute is 60, 0, 0, ..., 0.
The maximum TPS of the instance is 60 requests/second.
If 40 messages are sent in the first second and 20 messages are sent in the second second, the TPS for each second of that minute is 40, 20, 0, 0, ..., 0.
The maximum TPS of the instance is 40 requests/second.