ELB Monitoring Metrics
Overview
This section describes the namespace, the metrics that can be monitored by Cloud Eye, and dimensions of these metrics. You can view the metrics reported by ELB and the generated alarms on the Cloud Eye console.
Namespace
SYS.ELB
Metrics
For dedicated load balancers, you can view the monitoring metrics by load balancer, listener, backend server group, or AZ. You can view only the Layer 7 metrics of a backend server group.
Metric ID |
Name |
Description |
Value |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections from the monitored object to backend servers. Load balancing at Layer 7: total number of TCP connections from the clients to the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer |
1 minute |
m2_act_conn |
Active Connections |
Number of TCP and UDP connections in the ESTABLISHED state between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
Dedicated load balancer |
1 minute |
m3_inact_conn |
Inactive Connections |
Number of TCP connections between the monitored object and backend servers except those in the ESTABLISHED state. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
Dedicated load balancer |
1 minute |
m4_ncps |
New Connections |
Number of connections established between clients and the monitored object per second. Unit: packets/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m5_in_pps |
Incoming Packets |
Number of packets received by the monitored object per second. Unit: packets/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m6_out_pps |
Outgoing Packets |
Number of packets sent from the monitored object per second. Unit: packets/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m7_in_Bps |
Inbound Rate |
Traffic used for accessing the monitored object from the Internet. Unit: bytes/s |
≥ 0 byte/s |
Dedicated load balancer |
1 minute |
m8_out_Bps |
Outbound Rate |
Traffic used by the monitored object to access the Internet per second. Unit: bytes/s |
≥ 0 byte/s |
Dedicated load balancer |
1 minute |
m9_abnormal_servers |
Unhealthy Servers |
Number of unhealthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer |
1 minute |
ma_normal_servers |
Healthy Servers |
Number of healthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer |
1 minute |
m22_in_bandwidth |
Inbound Bandwidth |
Bandwidth used for accessing the monitored object from the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
m23_out_bandwidth |
Outbound Bandwidth |
Bandwidth used by the monitored object to access the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
m26_in_bandwidth_ipv6 |
IPv6 Inbound Bandwidth |
IPv6 network bandwidth used for accessing the monitored object from the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
m27_out_bandwidth_ipv6 |
IPv6 Outbound Bandwidth |
IPv6 network bandwidth used by the monitored object to access the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
Number of reset packets sent from backend servers to clients. These reset packets are generated by the backend servers and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m21_client_rps |
Reset Packets from Clients |
Number of reset packets sent by clients to backend servers. These reset packets are generated by clients and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancers |
Number of reset packets generated by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
mb_l7_qps |
Layer-7 Query Rate |
Number of requests the monitored object receives per second. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
mc_l7_http_2xx |
Layer-7 2xx Status Codes |
Number of 2xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
md_l7_http_3xx |
Layer-7 3xx Status Codes |
Number of 3xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
me_l7_http_4xx |
Layer-7 4xx Status Codes |
Number of 4xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
mf_l7_http_5xx |
Layer-7 5xx Status Codes |
Number of 5xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m10_l7_http_other_status |
Layer-7 Other Status Codes |
Number of status codes returned by the load balancer and backend servers except 2xx, 3xx, 4xx, and 5xx status codes. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m11_l7_http_404 |
Layer-7 404 Not Found |
Number of 404 Not Found status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m12_l7_http_499 |
Layer-7 499 Client Closed Request |
Number of 499 Client Closed Request status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m13_l7_http_502 |
Layer-7 502 Bad Gateway |
Number of 502 Bad Gateway status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m14_l7_rt |
Average Layer-7 Response Time |
Average response time of the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very long. This metric cannot be used as a reference. |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes Backend |
Number of 4xx status codes returned by the backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes Backend |
Number of 5xx status codes returned by the backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very long. This metric cannot be used as a reference. |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m1c_l7_rt_max |
Maximum Layer-7 Response Time |
Maximum response time of the monitored object. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m1d_l7_rt_min |
Minimum Layer-7 Response Time |
Minimum response time of the monitored object. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
Dedicated load balancer |
1 minute |
m25_l7_resp_Bps |
Backend Server Response Bandwidth |
The bandwidth that the monitored object uses to return response to clients. Unit: bits/s NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
m24_l7_req_Bps |
Backend Server Request Bandwidth |
The bandwidth that the monitored object uses to receive requests from clients. Unit: bits/s NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 bit/s |
Dedicated load balancer |
1 minute |
l7_con_usage |
Layer-7 Concurrent Connection Usage |
Ratio of HTTP and HTTPS connections established between the monitored object and backend servers per second, to the maximum number of concurrent connections allowed per second. Unit: percentage (%) |
≥ 0% |
Dedicated load balancer |
1 minute |
l7_in_bps_usage |
Layer-7 Inbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to receive requests from clients over HTTP and HTTPS, to the maximum inbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
Dedicated load balancer |
1 minute |
l7_out_bps_usage |
Layer-7 Outbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to return response to clients over HTTP and HTTPS, to the maximum outbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
Dedicated load balancer |
1 minute |
l7_ncps_usage |
Layer-7 New Connection Usage |
Ratio of HTTP and HTTPS connections established between clients and the monitored object per second, to the maximum number of new connections allowed per second. Unit: percentage (%) |
≥ 0% |
Dedicated load balancer |
1 minute |
l7_qps_usage |
Layer 7 QPS Usage |
Ratio of HTTP and HTTPS queries per second on the monitored object, to the maximum number of queries allowed per second. Unit: percentage (%) |
≥ 0% |
Dedicated load balancer |
1 minute |
l4_con_usage |
Layer-4 Concurrent Connection Usage |
Ratio of TCP and UDP connections established between the monitored object and backend servers per second, to the maximum number of concurrent connections allowed per second. Unit: percentage (%) |
≥ 0% |
Dedicated load balancer |
1 minute |
l4_in_bps_usage |
Layer-4 Inbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to receive requests from clients over TCP and UDP, to the maximum inbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
Dedicated load balancer |
1 minute |
l4_out_bps_usage |
Layer-4 Outbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to return response to clients over TCP and UDP, to the maximum outbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
Dedicated load balancer |
1 minute |
l4_ncps_usage |
Layer-4 New Connection Usage |
Ratio of TCP and UDP connections established between clients and the monitored object per second, to the maximum number of new connections allowed per second. Unit: percentage (%) |
≥ 0% |
Dedicated load balancer |
1 |
Metric ID |
Name |
Description |
Value |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections from the monitored object to backend servers. Load balancing at Layer 7: total number of TCP connections from the clients to the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer - listener |
1 minute |
m2_act_conn |
Active Connections |
Number of TCP and UDP connections in the ESTABLISHED state between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
Dedicated load balancer - listener |
1 minute |
m3_inact_conn |
Inactive Connections |
Number of TCP connections between the monitored object and backend servers except those in the ESTABLISHED state. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
Dedicated load balancer - listener |
1 minute |
m4_ncps |
New Connections |
Number of connections established between clients and the monitored object per second. Unit: packets/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m5_in_pps |
Incoming Packets |
Number of packets received by the monitored object per second. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 |
m6_out_pps |
Outgoing Packets |
Number of packets sent from the monitored object per second. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m7_in_Bps |
Inbound Rate |
Traffic used for accessing the monitored object from the Internet. Unit: bytes/s |
≥ 0 byte/s |
Dedicated load balancer - listener |
1 minute |
m8_out_Bps |
Outbound Rate |
Traffic used by the monitored object to access the Internet per second. Unit: bytes/s |
≥ 0 byte/s |
Dedicated load balancer - listener |
1 minute |
m9_abnormal_servers |
Unhealthy Servers |
Number of unhealthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer - listener |
1 minute |
ma_normal_servers |
Healthy Servers |
Number of healthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer - listener |
1 minute |
m22_in_bandwidth |
Inbound Bandwidth |
Bandwidth used for accessing the monitored object from the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer - listener |
1 minute |
m23_out_bandwidth |
Outbound Bandwidth |
Bandwidth used by the monitored object to access the Internet. Unit: bits/s |
≥ 0 bit/s |
Dedicated load balancer - listener |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
Number of reset packets sent from backend servers to clients. These reset packets are generated by the backend servers and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m21_client_rps |
Reset Packets from Clients |
Number of reset packets sent by clients to backend servers. These reset packets are generated by clients and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancers |
Number of reset packets generated by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
mb_l7_qps |
Layer-7 Query Rate |
Number of requests the monitored object receives per second. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
mc_l7_http_2xx |
Layer-7 2xx Status Codes |
Number of 2xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
md_l7_http_3xx |
Layer-7 3xx Status Codes |
Number of 3xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
me_l7_http_4xx |
Layer-7 4xx Status Codes |
Number of 4xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
mf_l7_http_5xx |
Layer-7 5xx Status Codes |
Number of 5xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m10_l7_http_other_status |
Layer-7 Other Status Codes |
Number of status codes returned by the monitored object except 2xx, 3xx, 4xx, and 5xx status codes. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m11_l7_http_404 |
Layer-7 404 Not Found |
Number of 404 Not Found status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m12_l7_http_499 |
Layer-7 499 Client Closed Request |
Number of 499 Client Closed Request status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m13_l7_http_502 |
Layer-7 502 Bad Gateway |
Number of 502 Bad Gateway status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m14_l7_rt |
Average Layer-7 Response Time |
Average response time of the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very high. This metric cannot be used as a reference. |
≥ 0 ms |
Dedicated load balancer - listener |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes Backend |
Number of 4xx status codes returned by the backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes Backend |
Number of 5xx status codes returned by the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - listener |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very long. This metric cannot be used as a reference. |
≥ 0 ms |
Dedicated load balancer - listener |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms |
≥ 0 ms |
Dedicated load balancer - listener |
1 |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms |
≥ 0 ms |
Dedicated load balancer - listener |
1 minute |
m1c_l7_rt_max |
Maximum Layer-7 Response Time |
Maximum response time of the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms |
≥ 0 ms |
Dedicated load balancer - listener |
1 minute |
m1d_l7_rt_min |
Minimum Layer-7 Response Time |
Minimum response time of the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms |
≥ 0 ms |
Dedicated load balancer - listener |
1 minute |
Metric ID |
Name |
Description |
Value |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
m9_abnormal_servers |
Unhealthy Servers |
Number of unhealthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer - backend server group |
1 minute |
ma_normal_servers |
Healthy Servers |
Number of healthy backend servers associated with the monitored object. Unit: Count |
≥ 0 |
Dedicated load balancer - backend server group |
1 minute |
mb_l7_qps |
Layer-7 Query Rate |
Number of requests the monitored object receives per second. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - backend server group |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very long. This metric cannot be used as a reference. |
≥ 0 ms |
Dedicated load balancer - backend server group |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms |
≥ 0 ms |
Dedicated load balancer - backend server group |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms |
≥ 0 ms |
Dedicated load balancer - backend server group |
1 minute |
m18_l7_upstream_2xx |
2xx Status Codes Backend |
Number of 2xx status codes returned by the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - backend server group |
1 minute |
m19_l7_upstream_3xx |
3xx Status Codes Backend |
Number of 3xx status codes returned by the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - backend server group |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes Backend |
Number of 4xx status codes returned by the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - backend server group |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes Backend |
Number of 5xx status codes returned by the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
Dedicated load balancer - backend server group |
1 minute |
m25_l7_resp_Bps |
Backend Server Response Bandwidth |
The bandwidth that the monitored object uses to return response to clients. Unit: bits/s NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 bit/s |
Dedicated load balancer - backend server group |
1 minute |
m24_l7_req_Bps |
Backend Server Request Bandwidth |
The bandwidth that the monitored object uses to receive requests from clients. Unit: bits/s NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 bit/s |
Dedicated load balancer - backend server group |
1 minute |
Metric ID |
Name |
Description |
Value |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections from the monitored object to backend servers. Load balancing at Layer 7: total number of TCP connections from the clients to the monitored object. Unit: Count |
≥ 0 |
AZ |
1 minute |
m2_act_conn |
Active Connections |
Number of TCP and UDP connections in the ESTABLISHED state between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
AZ |
1 minute |
m3_inact_conn |
Inactive Connections |
Number of TCP connections between the monitored object and backend servers except those in the ESTABLISHED state. You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: Count |
≥ 0 |
AZ |
1 minute |
m4_ncps |
New Connections |
Number of connections established between clients and the monitored object per second. Unit: packets/s |
≥ 0/s |
AZ |
1 minute |
m5_in_pps |
Incoming Packets |
Number of packets received by the monitored object per second. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m6_out_pps |
Outgoing Packets |
Number of packets sent from the monitored object per second. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m7_in_Bps |
Inbound Rate |
Traffic used for accessing the monitored object from the Internet. Unit: bytes/s |
≥ 0 byte/s |
AZ |
1 minute |
m8_out_Bps |
Outbound Rate |
Traffic used by the monitored object to access the Internet per second. Unit: bytes/s |
≥ 0 byte/s |
AZ |
1 minute |
m26_in_bandwidth_ipv6 |
IPv6 Inbound Bandwidth |
IPv6 network bandwidth used for accessing the monitored object from the Internet. Unit: bits/s |
≥ 0 bit/s |
AZ |
1 minute |
m27_out_bandwidth_ipv6 |
IPv6 Outbound Bandwidth |
IPv6 network bandwidth used by the monitored object to access the Internet. Unit: bits/s |
≥ 0 bit/s |
AZ |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
Number of reset packets sent from backend servers to clients. These reset packets are generated by the backend servers and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m21_client_rps |
Reset Packets from Clients |
Number of reset packets sent by clients to backend servers. These reset packets are generated by clients and then forwarded by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancers |
Number of reset packets generated by the load balancer. This metric is available only for TCP listeners. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
mb_l7_qps |
Layer-7 Query Rate |
Number of requests the monitored object receives per second. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
mc_l7_http_2xx |
Layer-7 2xx Status Codes |
Number of 2xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
md_l7_http_3xx |
Layer-7 3xx Status Codes |
Number of 3xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
me_l7_http_4xx |
Layer-7 4xx Status Codes |
Number of 4xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
mf_l7_http_5xx |
Layer-7 5xx Status Codes |
Number of 5xx status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m10_l7_http_other_status |
Layer-7 Other Status Codes |
Number of status codes returned by the load balancer and backend servers except 2xx, 3xx, 4xx, and 5xx status codes. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m11_l7_http_404 |
Layer-7 404 Not Found |
Number of 404 Not Found status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m12_l7_http_499 |
Layer-7 499 Client Closed Request |
Number of 499 Client Closed Request status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m13_l7_http_502 |
Layer-7 502 Bad Gateway |
Number of 502 Bad Gateway status codes returned by the load balancer and backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m14_l7_rt |
Average Layer-7 Response Time |
Average response time of the monitored object. This metric is available only when the frontend protocol is HTTP or HTTPS. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very long. This metric cannot be used as a reference. |
≥ 0 ms |
AZ |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes Backend |
Number of 4xx status codes returned by the backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes Backend |
Number of 5xx status codes returned by the backend servers. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: Count/s |
≥ 0/s |
AZ |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms NOTE:
The average response time it takes to establish a WebSocket connection may be very high. This metric cannot be used as a reference. |
≥ 0 ms |
AZ |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
AZ |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of backend servers. The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
AZ |
1 minute |
m1c_l7_rt_max |
Maximum Layer-7 Response Time |
Maximum response time of the monitored object. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
AZ |
1 minute |
m1d_l7_rt_min |
Minimum Layer-7 Response Time |
Minimum response time of the monitored object. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. This metric is available only when the frontend protocol is HTTP or HTTPS. Unit: ms |
≥ 0 ms |
AZ |
1 minute |
l4_con_usage |
Layer-4 Concurrent Connection Usage |
Ratio of TCP and UDP connections established between the monitored object and backend servers per second, to the maximum number of concurrent connections allowed per second. Unit: percentage (%) |
≥ 0% |
AZ |
1 minute |
l4_in_bps_usage |
Layer-4 Inbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to receive requests from clients over TCP and UDP, to the maximum inbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
AZ |
1 minute |
l4_out_bps_usage |
Layer-4 Outbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to return response to clients over TCP and UDP, to the maximum outbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
AZ |
1 minute |
l4_ncps_usage |
Layer-4 New Connection Usage |
Ratio of TCP and UDP connections established between clients and the monitored object per second, to the maximum number of new connections allowed per second. Unit: percentage (%) |
≥ 0% |
AZ |
1 minute |
l7_in_bps_usage |
Layer-7 Inbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to receive requests from clients over HTTP and HTTPS, to the maximum inbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
AZ |
1 minute |
l7_out_bps_usage |
Layer-7 Outbound Bandwidth Usage |
Ratio of the bandwidth that the monitored object uses to return response to clients over HTTP and HTTPS, to the maximum outbound bandwidth allowed. Unit: percentage (%) CAUTION:
If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed. |
≥ 0% |
AZ |
1 minute |
l7_con_usage |
Layer-7 Concurrent Connection Usage |
Ratio of HTTP and HTTPS connections established between the monitored object and backend servers per second, to the maximum number of concurrent connections allowed per second. Unit: percentage (%) |
≥ 0% |
AZ |
1 minute |
l7_ncps_usage |
Layer-7 New Connection Usage |
Ratio of HTTP and HTTPS connections established between clients and the monitored object per second, to the maximum number of new connections allowed per second. Unit: percentage (%) |
≥ 0% |
AZ |
1 minute |
l7_qps_usage |
Layer 7 QPS Usage |
Ratio of HTTP and HTTPS queries per second on the monitored object, to the maximum number of queries allowed per second. Unit: percentage (%) |
≥ 0% |
AZ |
1 minute |
Dimensions
Key |
Value |
---|---|
lbaas_instance_id |
ID of a dedicated load balancer. |
lbaas_listener_id |
ID of a listener added to a dedicated load balancer. |
lbaas_pool_id |
ID of a backend server group. |
available_zone |
AZ where a dedicated load balancer works. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot