ELB Metrics

Classic Load Balancer Metrics

Metric ID	Metric	Description	Monitored Object & Dimension	Monitoring Period (Raw Data)
m1_cps	Concurrent Connections	Number of TCP and UDP connections between the monitored object and backend servers Unit: Count	Monitored object: classic load balancer Dimension: lb_instance_id	1 minute
m2_act_conn	Active Connections	Number of TCP or 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): Unit: Count		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): Unit: Count		1 minute
m4_ncps	New Connections	Number of TCP and UDP connections established between clients and the monitored object per second Unit: Count/s		1 minute
m5_in_pps	Incoming Packets	Number of packets received by the monitored object per second Unit: Packet/s		1 minute
m6_out_pps	Outgoing Packets	Number of packets sent from the monitored object per second Unit: Packet/s		1 minute
m7_in_Bps	Inbound Rate	Traffic used for accessing the monitored object from the Internet Unit: byte/s		1 minute
m8_out_Bps	Outbound Rate	Traffic used by the monitored object to access the Internet Unit: byte/s		1 minute
m9_abnormal_servers	Unhealthy Servers	Number of unhealthy backend servers associated with the monitored object Unit: Count		1 minute
ma_normal_servers	Healthy Servers	Number of healthy backend servers associated with the monitored object Unit: Count		1 minute

Metrics of Shared Load Balancers and Shared Load Balancer Listeners

Metric ID	Metric	Description	Monitored Object & Dimension	Monitoring Period (Raw Data)
m1_cps	Concurrent Connections	Number of TCP and UDP connections between the monitored object and backend servers Unit: Count	Monitored object: shared load balancer and shared load balancer listener Dimensions^a: lbaas_instance_id and lbaas_listener_id	1 minute
m2_act_conn	Active Connections	Number of TCP or 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): Unit: Count		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): Unit: Count		1 minute
m4_ncps	New Connections	Number of TCP and UDP connections established between clients and the monitored object per second Unit: Count/s		1 minute
m5_in_pps	Incoming Packets	Number of packets received by the monitored object per second Unit: Packet/s		1 minute
m6_out_pps	Outgoing Packets	Number of data packets sent from the monitored object per second Unit: Packet/s		1 minute
m7_in_Bps	Inbound Rate	Traffic used for accessing the monitored object from the Internet Unit: byte/s		1 minute
m8_out_Bps	Outbound Rate	Traffic used by the monitored object to access the Internet Unit: byte/s		1 minute
m9_abnormal_servers	Unhealthy Servers	Number of unhealthy backend servers associated with the monitored object Unit: Count		1 minute
ma_normal_servers	Healthy Servers	Number of healthy backend servers associated with the monitored object Unit: Count		1 minute

a: If a service has multiple dimensions, all dimensions are mandatory when you use APIs to query the metrics.

Example of querying a single metric from both dimensions: dim.0=lbaas_instance_id,223e9eed-2b02-4ed2-a126-7e806a6fee1f&dim.1=lbaas_listener_id,3baa7335-8886-4867-8481-7cbba967a917

Example of querying metrics in batches from both dimensions:

"dimensions": [
{
"name": "lbaas_instance_id",
"value": "223e9eed-2b02-4ed2-a126-7e806a6fee1f"
}
{
"name": "lbaas_listener_id",
"value": "3baa7335-8886-4867-8481-7cbba967a917"
}
],

Parent topic: Network

Previous topic: EIP and Bandwidth Metrics

Next topic: FAQs