Tencent Cloud CKafka¶
The displayed Metrics of Tencent Cloud CKafka include message throughput, latency, concurrent connections, and reliability. These Metrics reflect the performance and reliability guarantees of CKafka in handling large-scale message delivery and real-time data streams.
Configuration¶
Install Func¶
It is recommended to activate the Guance Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed. Please proceed with the script installation.
If you need to deploy Func manually, refer to Manual Deployment of Func
Activate Script¶
Note: Please prepare the required Tencent Cloud AK in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess)
Activate Script for DataFlux Func (Automata)¶
- Log in to the Guance console.
- Click the 【Integration】 menu and select 【Cloud Account Management】.
- Click 【Add Cloud Account】, select 【Tencent Cloud】, and fill in the required information on the interface. If you have already configured the cloud account information, you can skip this step.
- Click 【Test】. After the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again.
- Click 【Cloud Account Management】. You can see the added cloud account in the list. Click the corresponding cloud account to enter the details page.
- Click the 【Integration】 button on the cloud account details page. In the
Not Installedlist, findTencent Cloud CKafkaand click the 【Install】 button. The installation interface will pop up for installation.
Activate Script Manually¶
-
Log in to the Func console, click 【Script Market】, and enter the Guance script market. Search for
integration_tencentcloud_ckafka. -
Click 【Install】, then enter the corresponding parameters: Tencent Cloud AK, SK, and account name.
-
Click 【Deploy Startup Script】. The system will automatically create the
Startupscript set and configure the corresponding startup scripts. -
After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs.
Verification¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration. You can also check the corresponding task records and logs to see if there are any exceptions.
- In Guance, check if the asset information exists in 「Infrastructure / Custom」.
- In Guance, check if there is corresponding monitoring data in 「Metrics」.
Metrics¶
After configuring Tencent Cloud Cloud Monitoring, the default Measurement is as follows. You can collect more Metrics through configuration. Tencent Cloud Cloud Monitoring Metrics Details
Performance Metrics¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimension |
|---|---|---|---|---|
| InstanceProCount | Instance Production Message Count | Instance production message count, summed according to the selected time granularity | Count | instanceId |
| InstanceConCount | Instance Consumption Message Count | Instance consumption message count, summed according to the selected time granularity | Count | instanceId |
| InstanceConReqCount | Instance Consumption Request Count | Instance-level consumption request count, summed according to the selected time granularity | Times | instanceId |
| InstanceProReqCount | Instance Production Request Count | Instance-level production request count, summed according to the selected time granularity | Times | instanceId |
System Metrics¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimension |
|---|---|---|---|---|
| InstanceDiskUsage | Disk Usage Percentage | Current disk usage as a percentage of the total disk capacity of the instance specification | % | instanceId |
Cumulative Usage Metrics¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimension |
|---|---|---|---|---|
| InstanceConnectCount | Instance Connection Count | Connection count between client and server | Count | instanceId |
| InstanceConFlow | Instance Consumption Flow | Instance consumption flow (excluding the flow generated by replicas), summed according to the selected time granularity | MB | instanceId |
| InstanceMaxConFlow | Instance Consumption Message Peak Bandwidth | Instance consumption message peak bandwidth (no replica concept during consumption) | MB/s | instanceId |
| InstanceMaxProFlow | Instance Production Message Peak Bandwidth | Instance production message peak bandwidth (excluding the bandwidth generated by replicas) | MB/s | instanceId |
| InstanceMsgCount | Instance Disk Message Total Count | Instance disk message total count (excluding replicas), taking the latest value according to the selected time granularity | Count | instanceId |
| InstanceMsgHeap | Instance Disk Usage | Instance disk usage (including replicas), taking the latest value according to the selected time granularity | MB | instanceId |
| InstanceProFlow | Instance Production Bandwidth | Instance production flow (excluding the flow generated by replicas), summed according to the selected time granularity | MB | instanceId |
| InstanceConnectPercentage | Instance Connection Count Percentage | Instance connection count percentage (percentage of client and server connections to quota) | % | instanceId |
| InstanceConsumeBandwidthPercentage | Instance Consumption Bandwidth Percentage | Instance consumption bandwidth percentage (percentage of instance consumption bandwidth to quota) | % | instanceId |
| InstanceConsumeGroupNum | Instance Consumption Group Count | Instance consumption group count | Count | instanceId |
| InstanceConsumeGroupPercentage | Instance Consumption Group Percentage | Instance consumption group percentage (percentage of instance consumption group count to quota) | % | instanceId |
| InstanceConsumeThrottle | Instance Consumption Throttle Count | Instance consumption throttle count | Times | instanceId |
| InstancePartitionNum | Instance Partition Count | Instance partition count | Count | instanceId |
| InstancePartitionPercentage | Instance Partition Percentage (Percentage of Quota) | Instance partition percentage (percentage of quota) | % | instanceId |
| InstanceProduceBandwidthPercentage | Instance Production Bandwidth Percentage | Instance production bandwidth percentage (percentage of quota) | % | instanceId |
| InstanceProduceThrottle | Instance Production Throttle Count | Instance production throttle count | Times | instanceId |
| InstanceReplicaProduceFlow | Instance Production Message Peak Bandwidth | Instance production message peak bandwidth (including the bandwidth generated by replicas) | MB/s | instanceId |
| InstanceTopicNum | Instance Topic Count | Instance Topic count | Count | instanceId |
| InstanceTopicPercentage | Instance Topic Percentage | Instance Topic percentage (percentage of quota) | % | instanceId |
Object¶
The collected Tencent Cloud CKafka object data structure can be seen in 「Infrastructure - Custom」.
{
"Healthy": "1",
"account_name": "xxxx",
"InstanceType": "profession",
"RenewFlag": "0",
"SubnetId": "subnet-bp2jqhcj",
"Vip": "172.17.32.16",
"Bandwidth": "160",
"ZoneId": "200002",
"message": "{\"AllowDowngrade\": true, \"Bandwidth\": 160, \"ClusterType\": \"CLOUD_EKS_TSE\", \"CreateTime\": 1692066710, \"Cvm\": 1, \"DiskSize\": 200, \"DiskType\": \"CLOUD_BASIC\", \"ExpireTime\": -62170009580, \"Features\": [], \"Healthy\": 1, \"HealthyMessage\": \"\", \"InstanceId\": \"ckafka-jamo82wo\", \"InstanceName\": \"\\u672a\\u547d\\u540d\", \"InstanceType\": \"profession\", \"IsInternal\": 0, \"MaxPartitionNumber\": 400, \"MaxTopicNumber\": 200, \"PartitionNumber\": 3, \"PublicNetwork\": 3, \"PublicNetworkChargeType\": \"BANDWIDTH_POSTPAID_BY_HOUR\", \"RebalanceDeadLineTimeStamp\": \"0000-00-00 00:00:00\", \"RebalanceTime\": \"0000-00-00 00:00:00\", \"RegionId\": \"ap-shanghai\", \"RenewFlag\": 0, \"Status\": 1, \"SubnetId\": \"subnet-bp2jqhcj\", \"Tags\": [], \"TopicNum\": 1, \"Version\": \"2.4.1\", \"Vip\": \"172.17.32.16\", \"VipList\": [{\"Vip\": \"172.17.32.16\", \"Vport\": \"9092\"}], \"VpcId\": \"vpc-kcphyzty\", \"Vport\": \"9092\", \"ZoneId\": 200002, \"ZoneIds\": [200002, 200003]}",
"__docid": "CO_31e0187c3c5c2842b60f88a87c11eca0",
"InstanceId": "ckafka-jamo82wo",
"InstanceName": "未命名",
"Status": "1",
"VpcId": "vpc-kcphyzty",
"Cvm": "1",
"__namespace": "custom_object",
"cloud_provider": "tencentcloud",
"create_time": 1692089426315,
"DiskType": "CLOUD_BASIC",
"ExpireTime": "-62170009580",
"TopicNum": "1",
"VipList": "[{\"Vip\": \"172.17.32.16\", \"Vport\": \"9092\"}]",
"time": 1692089425851,
"IsInternal": "0",
"Vport": "9092",
"class": "tencentcloud_ckafka",
"date": 1692089425000,
"date_ns": 0,
"name": "ckafka-jamo82wo",
"CreateTime": "1692066710",
"DiskSize": "200",
"RegionId": "ap-shanghai",
"Version": "2.4.1"
}
Note: The fields in
tagsandfieldsmay change with subsequent updates.
Appendix¶
TencentCloud-CKafka「Regions and Availability」¶
Please refer to the official Tencent documentation: