- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
Overview
Tencent Cloud provides the TCOP service for all users by default; therefore, you do not need to manually activate it. TCOP will start collecting monitoring data only after a Tencent Cloud product is used.
TDMQ for RocketMQ allows you to monitor the resources created under your account, so that you can keep track of the status of your resources in real time. You can configure alarm rules for monitoring metrics. When a monitoring metric reaches the set alarm threshold, TCOP will notify you of exceptions in time via the configured notification channel.
Directions
Configuring an alarm policy
An alarm policy can determine whether an alarm notification should be sent based on the comparison between the monitoring metric and the given threshold in the selected time period. You can promptly take appropriate precautionary or remedial measures when the alarm is triggered by a TDMQ for RocketMQ status change. Properly configured alarm policies help improve the robustness and reliability of your applications.
Note
Be sure to configure alarms for your instance to prevent exceptions caused by traffic spikes or specification limits.
1. Log in to the TCOP console.
2. On the left sidebar, select Alarm Configuration > Alarm Policy and click Create.
3. On the alarm configuration page, select a policy type and instance, and set the alarm rule and notification template.
Policy Type: Select TDMQ/RocketMQ/Topic alarm.
Alarm Object: select the TDMQ for RocketMQ resource for which to configure the alarm policy.
Trigger Condition: You can select Select template or Configure manually. The latter is selected by default. For more information on manual configuration, see the description below. For more information on how to create a template, see Creating a trigger condition template.
Note
Metric: For example, if you select 1 minute as the statistical period for the "Heaped Messages" metric, then if the message retention volume exceeds the threshold for N consecutive data points, an alarm will be triggered.
Alarm Frequency: For example, "Alarm once every 30 minutes" means that there will be only one alarm triggered every 30 minutes if a metric exceeds the threshold in several consecutive statistical periods. Another alarm will be triggered only if the metric exceeds the threshold again in the next 30 minutes.
Notification Template: You can select an existing notification template or create one to set the alarm recipient objects and receiving channels.
4. Click Complete.
Note
Creating a trigger condition template
1. Log in to the TCOP console.
2. On the left sidebar, click Trigger Condition Template to enter the Template list page.
3. Click Create on the Trigger Condition Template page.
4. On the template creation page, configure the policy type.
Policy Type: Select TDMQ-RocketMQ-topic alarm.
Apply preset trigger conditions: Select this option and the system recommended alarm policy will be displayed.
5. After confirming that everything is correct, click Save.
6. Return to the Create Alarm Policy page, click Refresh, and the alarm policy template just configured will be displayed.
Alarm Metric Dimension
Currently, TDMQ for RocketMQ metrics are divided into the following dimensions. You can select corresponding metrics to monitor and configure alarms based on your needs:
Metric Dimension | Metric Description |
Cluster | Cluster-level data aggregation, such as the cluster's production/consumption speed and traffic, heaped message count, and traffic throttling times. |
Storage (only for exclusive clusters) | The remaining available storage space of the current exclusive cluster and the proportion of storage used. |
Node (only for exclusive clusters) | The load of each compute node in the current cluster |
Topic | The production/consumption speed and traffic of the selected topic and its heaped message count. |
Group | The number of online consumers (clients) of the selected consumer group, consumption speed and traffic, heaped message count, and dead letter count. |
Consumer groups under a topic | The metrics of multiple groups are divided based on the topics subscribed to, so as to display the consumption speed/traffic and heaped message count in the groups of a specific topic. |
Yes
No
Was this page helpful?