Huawei Cloud ELB
Collect Huawei Cloud ELB monitoring metrics
Configuration¶
Install Func¶
It is recommended to enable Guance integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed, please continue with the script installation.
If you want to deploy Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the Huawei Cloud AK that meets the requirements in advance (for simplicity, you can directly grant the global read-only permission
Tenant Guest)
Hosted Version Installation Script¶
- Log in to the Guance console.
- Click the 【Integration】 menu, and select 【Cloud Account Management】.
- Click 【Add Cloud Account】, select 【Huawei Cloud】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step.
- Click 【Test】, and after the test is successful, click 【Save】. If the test fails, please check whether the relevant configuration information is correct and test again.
- Click 【Cloud Account Management】, and 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, find
Huawei Cloud ELBunder theNot Installedlist, and click the 【Install】 button to pop up the installation interface for installation.
Manual Installation Script¶
-
Log in to the Func console, click 【Script Market】, enter the Guance script market, and search for
integration_huaweicloud_elb. -
Click 【Install】, and enter the corresponding parameters: Huawei 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 enabling, 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. Wait a moment, you can check 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 there is asset information in 「Infrastructure - Resource Catalog」.
- In Guance, check if there is corresponding monitoring data in 「Metrics」.
Metrics¶
Configure Huawei Cloud ELB metrics, you can collect more metrics by configuration Huawei Cloud ELB Metrics Details
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period（Original Metric） |
|---|---|---|---|---|---|
m1_cps |
Concurrent Connections | In the four-layer load balancer, it refers to the number of all TCP and UDP connections established from the measurement object to the backend server. In the seven-layer load balancer, it refers to the number of all TCP connections established from the client to the ELB. Unit: count | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
m2_act_conn |
Active Connections | The number of all TCP or UDP connections in the ESTABLISHED state established from the measurement object to the backend server. Both Windows and Linux servers can use the following command to view. netstat -anUnit: count |
≥ 0 | ||
m3_inact_conn |
Inactive Connections | The number of all TCP connections in states other than ESTABLISHED established from the measurement object to all backend servers. Both Windows and Linux servers can use the following command to view. netstat -anUnit: count |
≥ 0 | ||
m4_ncps |
New Connections | The number of new TCP and UDP connections established from the client to the measurement object per second. Unit: count/second | ≥ 0 | ||
m5_in_pps |
Inbound Packets | The number of packets received by the measurement object per second. Unit: count/second | ≥ 0 | ||
m6_out_pps |
Outbound Packets | The number of packets sent by the measurement object per second. Unit: count/second | ≥ 0 | ||
m7_in_Bps |
Network Inbound Rate | The traffic consumed by accessing the measurement object from the outside. Unit: bytes/second | ≥ 0 | ||
m8_out_Bps |
Network Outbound Rate | The traffic consumed by the measurement object accessing the outside. Unit: bytes/second | ≥ 0 | ||
m9_abnormal_servers |
Abnormal Hosts | The number of abnormal hosts in the backend of the monitoring object counted by health checks. Unit: count | ≥ 0 | Dedicated Load BalancerShared Load Balancer | 1 minute |
ma_normal_servers |
Normal Hosts | The number of normal hosts in the backend of the monitoring object counted by health checks. Unit: count | ≥ 0 | ||
m1e_server_rps |
Backend Server Resets | TCP listener exclusive metric. The number of reset (RST) packets sent by the backend server to the client through the measurement object per second. Unit: count/second | ≥ 0 | Shared Load BalancerShared Load Balancer Listener | 1 minute |
m21_client_rps |
Client Resets | TCP listener exclusive metric. The number of reset (RST) packets sent by the client to the backend server through the measurement object per second. Unit: count/second | ≥ 0 | ||
m1f_lvs_rps |
Load Balancer Resets | TCP listener exclusive metric. The number of reset (RST) packets generated by the measurement object per second. Unit: count/second | ≥ 0 | ||
m22_in_bandwidth |
Inbound Bandwidth | The bandwidth consumed by accessing the measurement object from the outside. Unit: bits/second | ≥ 0 | Shared Load BalancerShared Load Balancer Listener | 1 minute |
m23_out_bandwidth |
Outbound Bandwidth | The bandwidth consumed by the measurement object accessing the outside. Unit: bits/second | ≥ 0 | ||
mb_l7_qps |
Layer 7 Query Rate | The current layer 7 query rate of the measurement object. (Only for HTTP and HTTPS listeners) Unit: times/second. | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
md_l7_http_3xx |
Layer 7 Protocol Return Code (3XX) | The number of layer 7 3XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
mc_l7_http_2xx |
Layer 7 Protocol Return Code (2XX) | The number of layer 7 2XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
me_l7_http_4xx |
Layer 7 Protocol Return Code (4XX) | The number of layer 7 4XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
mf_l7_http_5xx |
Layer 7 Protocol Return Code (5XX) | The number of layer 7 5XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m10_l7_http_other_status |
Layer 7 Protocol Return Code (Others) | The number of layer 7 non-2XX,3XX,4XX,5XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m11_l7_http_404 |
Layer 7 Protocol Return Code (404) | The number of layer 7 404 status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m12_l7_http_499 |
Layer 7 Protocol Return Code (499) | The number of layer 7 499 status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m13_l7_http_502 |
Layer 7 Protocol Return Code (502) | The number of layer 7 502 status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m14_l7_rt |
Layer 7 Protocol RT Average | The current layer 7 average response time of the measurement object. (Only for HTTP and HTTPS listeners) From the time the measurement object receives the client request to the time the measurement object returns all responses to the client. Unit: milliseconds. Note: The RT average may be very large in the websocket scenario, and this metric cannot be used as a latency metric reference at this time. |
≥ 0 | ||
m15_l7_upstream_4xx |
Layer 7 Backend Return Code (4XX) | The number of layer 7 backend 4XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
m16_l7_upstream_5xx |
Layer 7 Backend Return Code (5XX) | The number of layer 7 backend 5XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m17_l7_upstream_rt |
Layer 7 Backend RT Average | The current layer 7 backend average response time of the measurement object. (Only for HTTP and HTTPS listeners) From the time the measurement object forwards the request to the backend server to the time the measurement object receives the response from the backend server. Unit: milliseconds.Note: The RT average may be very large in the websocket scenario, and this metric cannot be used as a latency metric reference at this time. |
≥ 0 | ||
m1a_l7_upstream_rt_max |
Layer 7 Backend RT Maximum | The current layer 7 backend maximum response time of the measurement object. (Only for HTTP and HTTPS listeners) From the time the measurement object forwards the request to the backend server to the time the measurement object receives the response from the backend server. Unit: milliseconds. | ≥ 0 | Dedicated Load BalancerShared Load BalancerDedicated Load Balancer ListenerShared Load Balancer Listener | 1 minute |
m1b_l7_upstream_rt_min |
Layer 7 Backend RT Minimum | The current layer 7 backend minimum response time of the measurement object. (Only for HTTP and HTTPS listeners) From the time the measurement object forwards the request to the backend server to the time the measurement object receives the response from the backend server. Unit: milliseconds. | ≥ 0 | ||
l7_con_usage |
Layer 7 Concurrent Connection Usage | The concurrent connection usage of the layer 7 ELB instance. Unit: percentage. | ≥ 0 | Dedicated Load Balancer | 1 minute |
l7_in_bps_usage |
Layer 7 Inbound Bandwidth Usage | The inbound bandwidth usage of the layer 7 ELB instance. Unit: percentageNote: If the inbound bandwidth usage reaches 100%, it means that the performance guarantee provided by the ELB specification has been exceeded. Your business can continue to use higher bandwidth, but for the part that exceeds the bandwidth, ELB cannot guarantee service availability metrics. | ≥ 0 | ||
l7_out_bps_usage |
Layer 7 Outbound Bandwidth Usage | The outbound bandwidth usage of the layer 7 ELB instance. Unit: percentageNote: If the outbound bandwidth usage reaches 100%, it means that the performance guarantee provided by the ELB specification has been exceeded. Your business can continue to use higher bandwidth, but for the part that exceeds the bandwidth, ELB cannot guarantee service availability metrics. | ≥ 0 | ||
l7_ncps_usage |
Layer 7 New Connection Usage | The new connection usage of the layer 7 ELB instance. Unit: percentage | ≥ 0 | ||
l7_qps_usage |
Layer 7 Query Rate Usage | The query rate usage of the layer 7 ELB instance. Unit: percentage | ≥ 0 | ||
m18_l7_upstream_2xx |
Layer 7 Backend Return Code (2XX) | The number of layer 7 backend 2XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | Dedicated Load Balancer Backend Server GroupShared Load Balancer Backend Server Group | 1 minute |
m19_l7_upstream_3xx |
Layer 7 Backend Return Code (3XX) | The number of layer 7 backend 3XX series status response codes of the current measurement object. (Only for HTTP and HTTPS listeners) Unit: count/second. | ≥ 0 | ||
m25_l7_resp_Bps |
Layer 7 Response Bandwidth | Unit: bits/second | ≥ 0 | ||
m24_l7_req_Bps |
Layer 7 Request Bandwidth | Unit: bits/second | ≥ 0 | ||
l4_con_usage |
Layer 4 Concurrent Connection Usage | The concurrent connection usage of the layer 4 ELB instance. Unit: percentage | ≥ 0 | Dedicated Load Balancer | 1 minute |
l4_in_bps_usage |
Layer 4 Inbound Bandwidth Usage | The inbound bandwidth usage of the layer 4 ELB instance. Unit: percentageNote: If the inbound bandwidth usage reaches 100%, it means that the performance guarantee provided by the ELB specification has been exceeded. Your business can continue to use higher bandwidth, but for the part that exceeds the bandwidth, ELB cannot guarantee service availability metrics. | ≥ 0 | ||
l4_out_bps_usage |
Layer 4 Outbound Bandwidth Usage | The outbound bandwidth usage of the layer 4 ELB instance. Unit: percentageNote: If the outbound bandwidth usage reaches 100%, it means that the performance guarantee provided by the ELB specification has been exceeded. Your business can continue to use higher bandwidth, but for the part that exceeds the bandwidth, ELB cannot guarantee service availability metrics. | ≥ 0 | ||
l4_ncps_usage |
Layer 4 New Connection Usage | The new connection usage of the layer 4 ELB instance. Unit: percentage | ≥ 0 |
Object¶
The collected Huawei Cloud ELB object data structure can be seen in 「Infrastructure - Resource Catalog」
{
"measurement": "huaweicloud_elb",
"tags": {
"RegionId" : "cn-north-4",
"project_id" : "c631f046252d4ebdaxxxxxxxxxx",
"enterprise_project_id" : "0824ss-xxxx-xxxx-xxxx-12334fedffg",
"instance_id" : "16b35ebaba1c44c39d9c24bae742ca97in02",
"instance_name" : "elb-xxxx"
},
"fields": {
"vip_subnet_id" : "674e9b42-xxxx-xxxx-xxxx-5abcc565b961",
"vip_port_id" : "f1df08c5-xxxx-xxxx-xxxx-de435a51007b",
"vip_address" : "7aa51dbfxxxxxxxxxdad3c4828b58",
"operating_status": "ONLINE",
"created_at" : "2022-06-22T02:41:57",
"listeners" : "{Instance JSON Data}",
"updated_at" : "2022-06-22T02:41:57",
"description" : ""
}
}
Note: The fields in
tags,fieldsmay change with subsequent updatesTip 1: The value of
tags.instance_idis the instance ID, as the unique identifier.Tip 2:
fields.listenersis a JSON serialized string.fields.operating_statusis the operating status of the load balancer. Value range: can be ONLINE and FROZEN. ```