Tencent Cloud EIP
Collect Tencent Cloud EIP Metrics
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.
For self-deployed Func, refer to Self-deployed Func
Install Script¶
Note: Please prepare the required Tencent Cloud AK in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess
).
-
Log in to the Func console, click 【Script Market】, enter the TrueWatch script market, and search for:
integration_tencentcloud_eip
. -
Click 【Install】, then enter the corresponding parameters: Tencent Cloud AK ID, AK Secret, and account name.
-
Click 【Deploy Startup Script】, the system will automatically create the
Startup
script set and configure the corresponding startup script. -
After enabling, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to immediately execute once without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs.
Verification¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the automatic trigger configuration, and check the corresponding task records and logs for any exceptions.
- In TrueWatch, check if asset information exists in 「Infrastructure - Resource Catalog」.
- In TrueWatch, check if there are corresponding monitoring data in 「Metrics」.
Metrics¶
After configuring Tencent Cloud Cloud Monitor, the default Measurement is as follows. You can collect more metrics through configuration. Tencent Cloud Cloud Monitor Metrics Details
Tencent Cloud EIP metrics are under the tencentcloud_QCE/LB
Measurement. The following are the related metric descriptions:
Metric Name | Metric Chinese Name | Metric Description | Unit | Statistical Granularity |
---|---|---|---|---|
VipIntraffic |
Inbound Bandwidth | Elastic IP inbound bandwidth | Mbps | 5s, 10s, 60s, 300s, 3600s, 86400s |
VipOuttraffic |
Outbound Bandwidth | Elastic IP outbound bandwidth | Mbps | 5s, 10s, 60s, 300s, 3600s, 86400s |
VipInpkg |
Inbound Packets | Elastic IP inbound packets | packets/sec | 5s, 10s, 60s, 300s, 3600s, 86400s |
VipOutpkg |
Outbound Packets | Elastic IP outbound packets | packets/sec | 5s, 10s, 60s, 300s, 3600s, 86400s |
AccOuttraffic |
Outbound Traffic | Elastic IP outbound traffic | MB | 5s, 10s, 60s, 300s, 3600s, 86400s |
IntrafficVipRatio |
Public Inbound Bandwidth Utilization | Public inbound bandwidth utilization | % | 5s, 10s, 60s, 300s, 3600s, 86400s |
OuttrafficVipRatio |
Public Outbound Bandwidth Utilization | Public outbound bandwidth utilization | % | 5s, 10s, 60s, 300s, 3600s, 86400s |
VipInDropPkts |
Inbound Packet Loss | Inbound packet loss | pps | 5s, 10s, 60s, 300s, 3600s, 86400s |
VipOutDropPkts |
Outbound Packet Loss | Outbound packet loss | pps | 5s, 10s, 60s, 300s, 3600s, 86400s |
Object¶
The collected Tencent Cloud EIP object data structure can be seen in 「Infrastructure - Resource Catalog」.
{
"measurement": "tencentcloud_eip",
"tags": {
"name" : "eip-xxxxxx",
"RegionId" : "ap-shanghai",
"AddressId" : "ap-shanghai-1",
"AddressName" : "xxxx",
"AddressStatus" : "BIND",
"AddressIp" : "119.45.172.xxx",
"AddressType" : "EIP",
"InternetServiceProvider" : "BGP",
"InternetChargeType" : "TRAFFIC_POSTPAID_BY_HOUR"
},
"fields": {
"IsEipDirectConnection" : false,
"IsArrears" : false,
"IsBlocked" : false,
"InstanceId" : "ins-mmxxxx",
"NetworkInterfaceId" : "eni-8xxxxx",
"PrivateAddressIp" : "10.206.0.16",
"CreatedTime" : "2024-06-11T08:10:57Z",
"CascadeRelease" : false,
"LocalBgp" : false,
"Bandwidth" : 1,
"EipAlgType" : "{EIP ALG enabled protocol types}",
"message" : "{Instance JSON data}"
}
}
Note: Fields in
tags
,fields
may change with subsequent updates. Note 1:tags.name
value is the instance ID, used as the unique identifier. Note 2:fields.message
is the JSON serialized string.