Tencent Cloud EIP
Collect Tencent Cloud EIP metrics data
Configuration¶
Install Func¶
It is recommended to activate Guance Integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with script installation
If deploying Func manually, refer to Manual Deployment of Func
Activate Script¶
Note: Please prepare a Tencent Cloud AK that meets the requirements in advance (for simplicity, you can grant global read-only permission
ReadOnlyAccess)
Activate Script for Automata¶
- Log in to the Guance console
- Click on the [Integration] menu, select [Cloud Account Management]
- Click [Add Cloud Account], select [Tencent Cloud], and fill in the required information on the interface. If the cloud account information has been configured before, ignore this step
- Click [Test], after successful testing, click [Save]. If the test fails, please check if the relevant configuration information is correct and retest
- In the [Cloud Account Management] list, you can see the added cloud account. Click on the corresponding cloud account to enter the details page
- Click the [Integration] button on the cloud account details page. Under the
Not Installedlist, findTencent Cloud EIP, click the [Install] button, and the installation interface will pop up for installation.
Manual Activation Script¶
-
Log in to the Func console, click [Script Market], enter the Guance script market, search for
integration_tencentcloud_eip -
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 automatically configure the corresponding startup script -
After activation, you can see the corresponding automatic trigger configuration in [Manage / Automatic Trigger Configuration]. Click [Execute] to execute 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, and you can also check the corresponding task records and logs to see if there are any exceptions
- In Guance, check if asset information exists in [Infrastructure - Resource Catalog]
- In Guance, check if there is corresponding monitoring data in [Metrics]
Metrics¶
After configuring Tencent Cloud Cloud Monitor, the default measurement is as follows. More metrics can be collected through configuration Tencent Cloud Cloud Monitor Metrics Details
Tencent Cloud EIP metrics are under the tencentcloud_QCE/LB measurement. The following are the relevant metric descriptions:
| Metric Name | Metric Chinese Name | Metric Description | Unit | Statistics 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 |
Objects¶
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 type}",
"message" : "{instance JSON data}"
}
}
Note: The fields in
tagsandfieldsmay change with subsequent updates Note 1:tags.namevalue is the instance ID, used as a unique identifier Note 2:fields.messageis a JSON serialized string ```