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
Load Balancer 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 Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections established between the monitored object and backend servers. Load balancing at Layer 7: total number of TCP connections established between clients and the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer |
1 minute |
m2_act_conn |
Active Connections |
The number of active TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
Dedicated load balancer |
1 minute |
m3_inact_conn |
Inactive Connections |
The number of inactive TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
Dedicated load balancer |
1 minute |
m4_ncps |
New Connections |
The number of new connections established between clients and the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m5_in_pps |
Incoming Packets |
The number of packets received by the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m6_out_pps |
Outgoing Packets |
The number of packets sent from the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m7_in_Bps |
Inbound Traffic Rate |
How fast the inbound traffic reaches the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m8_out_Bps |
Outbound Traffic Rate |
How fast the outbound traffic leaves the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m9_abnormal_servers |
Unhealthy Servers |
The number of unhealthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer |
1 minute |
ma_normal_servers |
Healthy Servers |
The number of healthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer |
1 minute |
m22_in_bandwidth |
Inbound Bandwidth |
The bandwidth used for accessing the monitored object from external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m23_out_bandwidth |
Outbound Bandwidth |
The bandwidth used by the monitored object to access external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m26_in_bandwidth_ipv6 |
IPv6 Inbound Bandwidth |
The IPv6 network bandwidth used for accessing the monitored object from external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m27_out_bandwidth_ipv6 |
IPv6 Outbound Bandwidth |
The IPv6 network bandwidth used by the monitored object to access external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
The number of reset packets sent by backend servers to clients per second. These reset packets are generated by the backend servers and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m21_client_rps |
Reset Packets from Clients |
The number of reset packets sent by clients to backend servers per second. These reset packets are generated by clients and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancer |
The number of reset packets generated by the load balancer per second. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
mb_l7_qps |
Layer 7 Query Rate |
The number of queries the monitored object receives per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
mc_l7_http_2xx |
2xx Status Codes (Total) |
The number of 2xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
md_l7_http_3xx |
3xx Status Codes (Total) |
The number of 3xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
me_l7_http_4xx |
4xx Status Codes (Total) |
The number of 4xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
mf_l7_http_5xx |
5xx Status Codes (Total) |
The number of 5xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m10_l7_http_other_status |
Other Status Codes (Total) |
The number of other status codes returned by the monitored object and backend servers per second at Layer 7. Excluded status codes: 2xx, 3xx, 404 Not Found, 499 Client Closed Request, and 502 Bad Gateway Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m11_l7_http_404 |
404 Not Found (Total) |
The number of 404 Not Found status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m12_l7_http_499 |
499 Client Closed Request (Total) |
The number of 499 Client Closed Request status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m13_l7_http_502 |
502 Bad Gateway (Total) |
The number of 502 Bad Gateway status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m14_l7_rt |
Average Layer 7 Response Time |
Average response time of the monitored object at Layer 7. Supported protocols: HTTP/HTTPS The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients.
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 |
ms |
1000 (SI) |
Dedicated load balancer |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes (Backend Servers) |
The number of 4xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes (Backend Servers) |
The number of 5xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers associated with the monitored object at Layer 7. 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. Supported protocols: HTTP/HTTPS
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 |
1000 (SI) |
Dedicated load balancer |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of the backend server associated with the monitored object at Layer 7. 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. Supported protocols: HTTP/HTTPS |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of the backend server associated with the monitored object at Layer 7. 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. Supported protocols: HTTP/HTTPS |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer |
1 minute |
m1c_l7_rt_max |
Maximum Layer 7 Response Time |
Maximum response time of the monitored object at Layer 7. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Supported protocols: HTTP/HTTPS |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer |
1 minute |
m1d_l7_rt_min |
Minimum Layer 7 Response Time |
Minimum response time of the monitored object at Layer 7. The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Supported protocols: HTTP/HTTPS |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer |
1 minute |
l7_con_usage |
Layer 7 Concurrent Connection Usage |
The percentage of concurrent connections that have been established at Layer 7. |
≥ 0 |
% |
N/A |
Dedicated load balancer |
1 minute |
l7_in_bps_usage |
Layer 7 Inbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to receive requests from clients at Layer 7.
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 |
% |
N/A |
Dedicated load balancer |
1 minute |
l7_out_bps_usage |
Layer 7 Outbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to return responses to clients at Layer 7.
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 |
% |
N/A |
Dedicated load balancer |
1 minute |
l7_ncps_usage |
Layer 7 New Connection Usage |
The percentage of new connections that have been established at Layer 7. |
≥ 0 |
% |
N/A |
Dedicated load balancer |
1 minute |
l7_qps_usage |
Layer 7 QPS Usage |
The percentage of queries that have been made to the load balancer per second at Layer 7. |
≥ 0 |
% |
N/A |
Dedicated load balancer |
1 minute |
l4_con_usage |
Layer 4 Concurrent Connection Usage |
The percentage of concurrent connections that have been established at Layer 4. |
≥ 0 |
% |
N/A |
Dedicated load balancer |
1 minute |
l4_in_bps_usage |
Layer 4 Inbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to receive requests from clients at Layer 4.
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 |
% |
N/A |
Dedicated load balancer |
1 minute |
l4_out_bps_usage |
Layer 4 Outbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to return responses to clients at Layer 4.
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 |
% |
N/A |
Dedicated load balancer |
1 minute |
l4_ncps_usage |
Layer 4 New Connection Usage |
The percentage of new connections that have been established at Layer 4. |
≥ 0 |
% |
N/A |
Dedicated load balancer |
1 minute |
Listener Metrics
Metric ID |
Name |
Description |
Value Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections established between the monitored object and backend servers. Load balancing at Layer 7: total number of TCP connections established between clients and the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer - listener |
1 minute |
m2_act_conn |
Active Connections |
The number of active TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
Dedicated load balancer - listener |
1 minute |
m3_inact_conn |
Inactive Connections |
The number of inactive TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
Dedicated load balancer - listener |
1 minute |
m4_ncps |
New Connections |
The number of new connections established between clients and the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m5_in_pps |
Incoming Packets |
The number of packets received by the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m6_out_pps |
Outgoing Packets |
The number of packets sent from the monitored object per second. |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m7_in_Bps |
Inbound Traffic Rate |
How fast the inbound traffic reaches the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m8_out_Bps |
Outbound Traffic Rate |
How fast the outbound traffic leaves the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m9_abnormal_servers |
Unhealthy Servers |
The number of unhealthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer - listener |
1 minute |
ma_normal_servers |
Healthy Servers |
The number of healthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer - listener |
1 minute |
m22_in_bandwidth |
Inbound Bandwidth |
The bandwidth used for accessing the monitored object from external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m23_out_bandwidth |
Outbound Bandwidth |
The bandwidth used by the monitored object to access external networks. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
The number of reset packets sent by backend servers to clients per second. These reset packets are generated by the backend servers and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m21_client_rps |
Reset Packets from Clients |
The number of reset packets sent by clients to backend servers per second. These reset packets are generated by clients and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancer |
The number of reset packets generated by the load balancer per second. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
mb_l7_qps |
Layer 7 Query Rate |
The number of queries the monitored object receives per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
mc_l7_http_2xx |
2xx Status Codes (Total) |
The number of 2xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
md_l7_http_3xx |
3xx Status Codes (Total) |
The number of 3xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
me_l7_http_4xx |
4xx Status Codes (Total) |
The number of 4xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
mf_l7_http_5xx |
5xx Status Codes (Total) |
The number of 5xx status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m10_l7_http_other_status |
Other Status Codes (Total) |
The number of other status codes returned by the monitored object and backend servers per second at Layer 7. Excluded status codes: 2xx, 3xx, 404 Not Found, 499 Client Closed Request, and 502 Bad Gateway Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m11_l7_http_404 |
404 Not Found (Total) |
The number of 404 Not Found status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m12_l7_http_499 |
499 Client Closed Request (Total) |
The number of 499 Client Closed Request status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m13_l7_http_502 |
502 Bad Gateway (Total) |
The number of 502 Bad Gateway status codes returned by the monitored object and backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m14_l7_rt |
Average Layer 7 Response Time |
Average response time of the monitored object at Layer 7. Supported protocols: HTTP/HTTPS The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients.
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 |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes (Backend Servers) |
The number of 4xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes (Backend Servers) |
The number of 5xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - listener |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers associated with the monitored object at Layer 7. Supported protocols: HTTP/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.
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 |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of the backend server associated with the monitored object at Layer 7. Supported protocols: HTTP/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. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of the backend server associated with the monitored object at Layer 7. Supported protocols: HTTP/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. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m1c_l7_rt_max |
Maximum Layer 7 Response Time |
Maximum response time of the monitored object at Layer 7. Supported protocols: HTTP/HTTPS The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
m1d_l7_rt_min |
Minimum Layer 7 Response Time |
Minimum response time of the monitored object at Layer 7. Supported protocols: HTTP/HTTPS The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - listener |
1 minute |
Backend Server Group Metrics
Metric ID |
Name |
Description |
Value Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
m9_abnormal_servers |
Unhealthy Servers |
The number of unhealthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer - backend server group |
1 minute |
ma_normal_servers |
Healthy Servers |
The number of healthy backend servers associated with the monitored object. |
≥ 0 |
Count |
N/A |
Dedicated load balancer - backend server group |
1 minute |
mb_l7_qps |
Layer 7 Query Rate |
The number of queries the monitored object receives per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - backend server group |
1 minute |
m17_l7_upstream_rt |
Average Server Response Time |
Average response time of backend servers associated with the monitored object at Layer 7. Supported protocols: HTTP/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.
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 |
1000 (SI) |
Dedicated load balancer - backend server group |
1 minute |
m1a_l7_upstream_rt_max |
Maximum Server Response Time |
Maximum response time of the backend server associated with the monitored object at Layer 7. Supported protocols: HTTP/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. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - backend server group |
1 minute |
m1b_l7_upstream_rt_min |
Minimum Server Response Time |
Minimum response time of the backend server associated with the monitored object at Layer 7. Supported protocols: HTTP/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. |
≥ 0 |
ms |
1000 (SI) |
Dedicated load balancer - backend server group |
1 minute |
m15_l7_upstream_4xx |
4xx Status Codes (Backend Servers) |
The number of 4xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - backend server group |
1 minute |
m16_l7_upstream_5xx |
5xx Status Codes (Backend Servers) |
The number of 5xx status codes returned by the backend servers per second at Layer 7. Supported protocols: HTTP/HTTPS |
≥ 0 |
Count/s |
N/A |
Dedicated load balancer - backend server group |
1 minute |
m25_l7_resp_Bps |
Layer 7 Response Bandwidth |
The bandwidth used by the backend servers associated with the monitored object to return responses to clients.
NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer - backend server group |
1 minute |
m24_l7_req_Bps |
Layer 7 Request Bandwidth |
The bandwidth used by the backend servers associated with the monitored object to receive requests from clients.
NOTE:
When HTTP/2 is enabled for a listener, this metric cannot be used as a reference. |
≥ 0 |
bit/s |
1000 (SI) |
Dedicated load balancer - backend server group |
1 minute |
AZ Metrics
Metric ID |
Name |
Description |
Value Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Load balancing at Layer 4: total number of TCP and UDP connections established between the monitored object and backend servers. Load balancing at Layer 7: total number of TCP connections established between the clients and the monitored object. |
≥ 0 |
Count |
N/A |
AZ |
1 minute |
m2_act_conn |
Active Connections |
The number of active TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
AZ |
1 minute |
m3_inact_conn |
Inactive Connections |
The number of inactive TCP and UDP connections established between the monitored object and backend servers. You can run the following command to view the connections (both Windows and Linux servers): netstat -an |
≥ 0 |
Count |
N/A |
AZ |
1 minute |
m4_ncps |
New Connections |
The number of new connections established between clients and the monitored object per second. |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
m5_in_pps |
Incoming Packets |
The number of packets received by the monitored object per second. |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
m6_out_pps |
Outgoing Packets |
The number of packets sent from the monitored object per second. |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
m7_in_Bps |
Inbound Traffic Rate |
How fast the inbound traffic reaches the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
AZ |
1 minute |
m8_out_Bps |
Outbound Traffic Rate |
How fast the outbound traffic leaves the monitored object. |
≥ 0 |
Byte/s |
1000 (SI) |
AZ |
1 minute |
m26_in_bandwidth_ipv6 |
IPv6 Inbound Bandwidth |
The IPv6 network bandwidth used for accessing the monitored object from external networks. |
≥ 0 |
bit/s |
1000 (SI) |
AZ |
1 minute |
m27_out_bandwidth_ipv6 |
IPv6 Outbound Bandwidth |
The IPv6 network bandwidth used by the monitored object to access external networks. |
≥ 0 |
bit/s |
1000 (SI) |
AZ |
1 minute |
m1e_server_rps |
Reset Packets from Backend Servers |
The number of reset packets sent by backend servers to clients per second. These reset packets are generated by the backend servers and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
m21_client_rps |
Reset Packets from Clients |
The number of reset packets sent by clients to backend servers per second. These reset packets are generated by clients and then forwarded by the load balancer. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
m1f_lvs_rps |
Reset Packets from Load Balancer |
The number of reset packets generated by the load balancer per second. Supported protocols: TCP |
≥ 0 |
Count/s |
N/A |
AZ |
1 minute |
l4_con_usage |
Layer 4 Concurrent Connection Usage |
The percentage of concurrent connections that have been established at Layer 4. |
≥ 0 |
% |
N/A |
AZ |
1 minute |
l4_in_bps_usage |
Layer 4 Inbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to receive requests from clients at Layer 4.
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 |
% |
N/A |
AZ |
1 minute |
l4_out_bps_usage |
Layer 4 Outbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to return responses to clients at Layer 4.
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 |
% |
N/A |
AZ |
1 minute |
l4_ncps_usage |
Layer 4 New Connection Usage |
The percentage of new connections that have been established at Layer 4. |
≥ 0 |
% |
N/A |
AZ |
1 minute |
l7_in_bps_usage |
Layer 7 Inbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to receive requests from clients at Layer 7.
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 |
% |
N/A |
AZ |
1 minute |
l7_out_bps_usage |
Layer 7 Outbound Bandwidth Usage |
The percentage of the bandwidth that the load balancer uses to return responses to clients at Layer 7.
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 |
% |
N/A |
AZ |
1 minute |
l7_con_usage |
Layer 7 Concurrent Connection Usage |
The percentage of concurrent connections that have been established at Layer 7. |
≥ 0 |
% |
N/A |
AZ |
1 minute |
l7_ncps_usage |
Layer 7 New Connection Usage |
The percentage of new connections that have been established at Layer 7. |
≥ 0 |
% |
N/A |
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.