Tencent Cloud provides the Cloud Monitor service for all users by default; therefore, you do not need to manually activate it. Cloud Monitor will start collecting monitoring data only after a Tencent Cloud product is used.
CKafka allows you to monitor the resources created under your account, including instances, topics, and consumer groups, 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, Cloud Monitor will notify you of exceptions in time via email, SMS, phone call, etc.
The created alarm 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 take appropriate precautionary or remedial measures in a timely manner when the alarm is triggered because the status of CKafka changes. Properly creating alarm policies can 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.
Note:
- Metric: For example, if you select 1 minute as the statistical period for the "Disk Utilization" metric, then if the disk utilization 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. For the metrics for which we recommend you configure an alarm policy, see Monitoring Alarm Policies Recommended for CKafka.
Note:For more information on alarms, see Creating Alarm Policy.
For more information on metrics that may affect the business data stability, see CKafka Data Reliability Description.
Based on user feedback, we recommend you configure alarm policies in the following three dimensions (six metrics in total) for CKafka, but you should configure them reasonably based on your actual business conditions.
Instance monitoring:
Monitoring Metric | Description |
---|---|
Production Peak Bandwidth (MB/s) | Peak traffic generated when the instance produces messages (excluding the traffic generated by replicas). |
Consumption Peak Bandwidth (MB/s) | Peak traffic generated when the instance consumes messages (there is no replica concept in consumption). |
Disk Utilization (%) | Ratio of the currently used disk capacity to the total disk capacity of the instance in percentages. |
Instance connections | Number of connections between the client and server. |
Topic monitoring:
Monitoring Metric | Description |
---|---|
Used Disk Capacity (MB) | Total size of messages in the topic (excluding those produced by replicas) that actually use disk capacity, which is the latest value in the selected time granularity. |
Consumer group:
Monitoring Metric | Description |
---|---|
Unconsumed Messages | Number of unconsumed messages in the consumer group. |
Was this page helpful?