Tencent Cloud CLB Private¶
Use the "TrueWatch Cloud Sync" series of script packages in the script market to synchronize cloud monitoring and cloud asset data to TrueWatch
Configuration¶
Install Func¶
It is recommended to activate TrueWatch Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed. Please proceed with the script installation.
If you deploy Func yourself, refer to Self-deploying Func
Install Script¶
Note: Please prepare the Tencent Cloud AK that meets the requirements in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess
).
To synchronize Tencent Cloud CLB monitoring data, we install the corresponding collection script: "TrueWatch Integration (Tencent Cloud-CLB Collection)" (ID: integration_tencentcloud_clb
).
Click 【Install】, then enter the corresponding parameters: Tencent Cloud AK, Tencent Cloud account name.
Click 【Deploy Startup Script】, the system will automatically create the Startup
script set and configure the corresponding startup script.
In addition, you can see the corresponding automatic trigger configuration in "Management / Automatic Trigger Configuration". Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs.
We have collected some configurations by default. For details, see the Metrics section Configure Custom Cloud Object Metrics
Verification¶
- In "Management / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and check the task records and logs for any exceptions.
- In TrueWatch, check whether the asset information exists in "Infrastructure / Custom".
- In TrueWatch, check whether there is corresponding monitoring data in "Metrics".
Metrics¶
After configuring Tencent Cloud-Cloud Monitoring, the default Measurement is as follows. More Metrics can be collected through configuration Tencent Cloud Cloud Monitoring Metrics Details
Metric Name | Metric Chinese Name | Description | Unit | Statistical Granularity |
---|---|---|---|---|
ClientConnum |
Active Connections from Client to LB | At a certain moment within the statistical granularity, the number of active connections from the client to the load balancer or listener. | Count | 10s、60s、300s |
ClientInactiveConn |
Inactive Connections from Client to LB | At a certain moment within the statistical granularity, the number of inactive connections from the client to the load balancer or listener. | Count | 10s、60s、300s |
ClientConcurConn |
Concurrent Connections from Client to LB | At a certain moment within the statistical granularity, the number of concurrent connections from the client to the load balancer or listener. | Count | 10s、60s、300s |
ClientNewConn |
New Connections from Client to LB | Within the statistical granularity, the number of new connections from the client to the load balancer or listener. | Count/second | 10s、60s、300s |
ClientInpkg |
Inbound Packets from Client to LB | Within the statistical granularity, the number of data packets sent by the client to the load balancer per second. | Packets/second | 10s、60s、300s |
ClientOutpkg |
Outbound Packets from Client to LB | Within the statistical granularity, the number of data packets sent by the load balancer to the client per second. | Packets/second | 10s、60s、300s |
ClientAccIntraffic |
Inbound Traffic from Client to LB | Within the statistical granularity, the traffic flowing from the client to the load balancer. | MB | 10s、60s、300s |
ClientAccOuttraffic |
Outbound Traffic from Client to LB | Within the statistical granularity, the traffic flowing from the load balancer to the client. | MB | 10s、60s、300s |
ClientOuttraffic |
Outbound Bandwidth from Client to LB | Within the statistical granularity, the bandwidth used by the load balancer to send data to the client. | Mbps | 10s、60s、300s |
ClientIntraffic |
Inbound Bandwidth from Client to LB | Within the statistical granularity, the bandwidth used by the client to send data to the load balancer. | Mbps | 10s、60s、300s |
OutTraffic |
Outbound Bandwidth from LB to Backend | Within the statistical granularity, the bandwidth used by the backend RS to send data to the load balancer. | Mbps | 60s、300s |
InTraffic |
Inbound Bandwidth from LB to Backend | Within the statistical granularity, the bandwidth used by the load balancer to send data to the backend RS. | Mbps | 60s、300s |
OutPkg |
Outbound Packets from LB to Backend | Within the statistical granularity, the number of data packets sent by the backend RS to the load balancer per second. | Packets/second | 60s、300s |
InPkg |
Inbound Packets from LB to Backend | Within the statistical granularity, the number of data packets sent by the load balancer to the backend RS per second. | Packets/second | 60s、300s |
ConNum |
Connections from LB to Backend | Within the statistical granularity, the number of connections from the load balancer to the backend RS. | Count | 60s、300s |
NewConn |
New Connections from LB to Backend | Within the statistical granularity, the number of new connections from the load balancer to the backend RS. | Count/minute | 60s、300s |
DropTotalConns |
Dropped Connections | Within the statistical granularity, the number of connections dropped by the load balancer or listener. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Count | 10s、60s、300s |
InDropBits |
Dropped Inbound Bandwidth | Within the statistical granularity, the bandwidth dropped when the client accesses the load balancer through the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Bytes | 10s、60s、300s |
OutDropBits |
Dropped Outbound Bandwidth | Within the statistical granularity, the bandwidth dropped when the load balancer accesses the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Bytes | 10s、60s、300s |
InDropPkts |
Dropped Inbound Packets | Within the statistical granularity, the number of data packets dropped when the client accesses the load balancer through the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Packets/second | 10s、60s、300s |
OutDropPkts |
Dropped Outbound Packets | Within the statistical granularity, the number of data packets dropped when the load balancer accesses the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Packets/second | 10s、60s、300s |
DropQps |
Dropped QPS | Within the statistical granularity, the number of requests dropped by the load balancer or listener. This metric is unique to layer 7 listeners. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. | Count | 60s、300s |
IntrafficVipRatio |
Inbound Bandwidth Utilization | Within the statistical granularity, the bandwidth utilization when the client accesses the load balancer through the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. This metric is in the beta stage. To use it, please submit a Work Order Application. | % | 10s、60s、300s |
OuttrafficVipRatio |
Outbound Bandwidth Utilization | Within the statistical granularity, the bandwidth utilization when the load balancer accesses the internal network. This metric is only supported for standard account types, not for traditional account types. For account type judgment, please refer to Judging Account Types. This metric is in the beta stage. To use it, please submit a Work Order Application. | % | 10s、60s、300s |
ReqAvg |
Average Request Time | Within the statistical granularity, the average request time of the load balancer. This metric is unique to layer 7 listeners. | Milliseconds | 60s、300s |
ReqMax |
Maximum Request Time | Within the statistical granularity, the maximum request time of the load balancer. This metric is unique to layer 7 listeners. | Milliseconds | 60s、300s |
RspAvg |
Average Response Time | Within the statistical granularity, the average response time of the load balancer. This metric is unique to layer 7 listeners. | Milliseconds | 60s、300s |
RspMax |
Maximum Response Time | Within the statistical granularity, the maximum response time of the load balancer. This metric is unique to layer 7 listeners. | Milliseconds | 60s、300s |
RspTimeout |
Response Timeout Count | Within the statistical granularity, the number of response timeouts of the load balancer. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
SuccReq |
Successful Requests per Minute | Within the statistical granularity, the number of successful requests per minute of the load balancer. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
TotalReq |
Requests per Second | Within the statistical granularity, the number of requests per second of the load balancer. This metric is unique to layer 7 listeners. | Count | 60s、300s |
ClbHttp3xx |
3xx Status Codes Returned by CLB | Within the statistical granularity, the number of 3xx status codes returned by the load balancer (the sum of status codes returned by the load balancer and backend server). This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
ClbHttp4xx |
4xx Status Codes Returned by CLB | Within the statistical granularity, the number of 4xx status codes returned by the load balancer (the sum of status codes returned by the load balancer and backend server). This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
ClbHttp5xx |
5xx Status Codes Returned by CLB | Within the statistical granularity, the number of 5xx status codes returned by the load balancer (the sum of status codes returned by the load balancer and backend server). This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
Http2xx |
2xx Status Codes | Within the statistical granularity, the number of 2xx status codes returned by the backend server. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
Http3xx |
3xx Status Codes | Within the statistical granularity, the number of 3xx status codes returned by the backend server. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
Http4xx |
4xx Status Codes | Within the statistical granularity, the number of 4xx status codes returned by the backend server. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
Http5xx |
5xx Status Codes | Within the statistical granularity, the number of 5xx status codes returned by the backend server. This metric is unique to layer 7 listeners. | Count/minute | 60s、300s |
UnhealthRsCount |
Unhealthy Health Checks | Within the statistical period, the number of unhealthy health checks of the load balancer. | Count | 60s、300s |
Object¶
The collected Tencent Cloud CLB Private object data structure can be seen in "Infrastructure - Custom".
{
"measurement": "tencentcloud_clb",
"tags": {
"name" : "lb-xxxx",
"RegionId" : "ap-shanghai",
"LoadBalancerId" : "lb-xxxx",
"LoadBalancerName": "lb-xxxx",
"Address" : "81.xxxx",
"LoadBalancerType": "Private",
"Status" : "1",
"VpcId" : "vpc-xxxx",
"Zone" : "ap-shanghai-3",
"ChargeType" : "POSTPAID_BY_HOUR"
},
"fields": {
"CreateTime": "2022-04-27 15:19:49",
"listeners" : "{Listener JSON Data}",
"message" : "{Instance JSON Data}"
}
}