This topic describes the CLB monitoring metrics, which help you assess the load and performance of your CLB instances and troubleshoot issues like request timeouts and traffic throttling.
Notes
When you call a CloudMonitor API operation, you must specify the Namespace, Period, MetricName, and Dimensions for the CLB instance.
The Namespace is
acs_slb_dashboard.The Period is the sampling granularity. The default value is 60 seconds. You can set this parameter to an integer multiple of 60.
Dimensions is a JSON string. Example:
[{"instanceId":"lb-bp1r92vzpemy099f******", "port":"80", "vip":"121.43.**.**"}]. In this string, Dimensions includeinstanceId(the ID of the CLB instance),port(the listener port of the CLB instance), andvip(the service address of the CLB instance).
CLB monitoring metrics
Metrics available in console, API, and SDK
Layer 4 protocol metrics
Metric type | Metric | Description | MetricName | Dimensions | Statistics |
Instance connections | New connections (instance) | The number of new TCP and UDP connections that the CLB instance processes per second. Unit: Count/s | InstanceNewConnection | instanceId | Average, Minimum, Maximum |
Dropped connections (instance) | The number of TCP and UDP connections that the CLB instance drops per second. Unit: Count/s | InstanceDropConnection | instanceId | Average, Minimum, Maximum | |
Active connections (instance) | The number of established TCP connections to the CLB instance. Unit: Count Note If you use persistent connections, a single connection can be used to transfer multiple file requests. | InstanceActiveConnection | instanceId | Average, Minimum, Maximum | |
Inactive connections (instance) | The number of TCP connections to the CLB instance not in the ESTABLISHED state, plus all UDP connections. Unit: Count | InstanceInactiveConnection | instanceId | Average, Minimum, Maximum | |
Concurrent connections (instance) | The total number of concurrent TCP and UDP connections that the CLB instance processes. Unit: Count | InstanceMaxConnection | instanceId | Average, Minimum, Maximum | |
Instance bandwidth/traffic | Inbound traffic (instance) | The amount of inbound TCP and UDP traffic the CLB instance receives per second. Unit: bit/s | InstanceTrafficRX | instanceId | Average, Minimum, Maximum |
Outbound traffic (instance) | The amount of outbound TCP and UDP traffic the CLB instance sends per second. Unit: bit/s | InstanceTrafficTX | instanceId | Average, Minimum, Maximum | |
Inbound packets (instance) | The number of inbound TCP and UDP packets the CLB instance receives per second. Unit: Count/s | InstancePacketRX | instanceId | Average, Minimum, Maximum | |
Outbound packets (instance) | The number of outbound TCP and UDP packets the CLB instance sends per second. Unit: Count/s | InstancePacketTX | instanceId | Average, Minimum, Maximum | |
Dropped inbound traffic (instance) | The amount of inbound TCP and UDP traffic that the CLB instance fails to receive per second. Unit: bit/s | InstanceDropTrafficRX | instanceId | Average, Minimum, Maximum | |
Dropped outbound traffic (instance) | The amount of outbound TCP and UDP traffic that the CLB instance fails to send per second. Unit: bit/s | InstanceDropTrafficTX | instanceId | Average, Minimum, Maximum | |
Dropped inbound packets (instance) | The number of inbound TCP and UDP packets that the CLB instance fails to receive per second. Unit: Count/s | InstanceDropPacketRX | instanceId | Average, Minimum, Maximum | |
Dropped outbound packets (instance) | The number of outbound TCP and UDP packets that the CLB instance fails to send per second. Unit: Count/s | InstanceDropPacketTX | instanceId | Average, Minimum, Maximum | |
Listener connections | New connections (listener) | The number of new TCP or UDP connections that the listener processes per second. Unit: Count/s | NewConnection | instanceId, port, vip | Average, Minimum, Maximum |
Dropped connections (listener) | The number of TCP or UDP connections that the listener drops per second. Unit: Count/s | DropConnection | instanceId, port, vip | Average, Minimum, Maximum | |
Active connections (listener) | The number of established TCP connections to the listener. Unit: Count Note If you use persistent connections, a single connection can be used to transfer multiple file requests. | ActiveConnection | instanceId, port, vip | Average, Minimum, Maximum | |
Inactive connections (listener) | The number of TCP connections to the listener not in the ESTABLISHED state, plus all UDP connections. Unit: Count | InactiveConnection | instanceId, port, vip | Average, Minimum, Maximum | |
Concurrent connections (listener) | The total number of concurrent TCP or UDP connections processed by the listener. Unit: Count | MaxConnection | instanceId, port, vip | Average, Minimum, Maximum | |
Listener bandwidth/traffic | Inbound traffic (listener) | The amount of inbound TCP or UDP traffic that is received by the listener per second. Unit: bit/s | TrafficRXNew | instanceId, port, vip | Average, Minimum, Maximum |
Outbound traffic (listener) | The amount of outbound TCP or UDP traffic that is sent from the listener per second. Unit: bit/s | TrafficTXNew | instanceId, port, vip | Average, Minimum, Maximum | |
Inbound packets (listener) | The number of inbound TCP or UDP packets that are received by the listener per second. Unit: Count/s | PacketRX | instanceId, port, vip | Average, Minimum, Maximum | |
Outbound packets (listener) | The number of outbound TCP or UDP packets that are sent from the listener per second. Unit: Count/s | PacketTX | instanceId, port, vip | Average, Minimum, Maximum | |
Dropped inbound traffic (listener) | The amount of inbound TCP or UDP traffic that the listener fails to receive per second. Unit: bit/s | DropTrafficRX | instanceId, port, vip | Average, Minimum, Maximum | |
Dropped outbound traffic (listener) | The amount of outbound TCP or UDP traffic that the listener fails to send per second. Unit: bit/s | DropTrafficTX | instanceId, port, vip | Average, Minimum, Maximum | |
Dropped inbound packets (listener) | The number of inbound TCP or UDP packets that the listener fails to receive per second. Unit: Count/s | DropPacketRX | instanceId, port, vip | Average, Minimum, Maximum | |
Dropped outbound packets (listener) | The number of outbound TCP or UDP packets that the listener fails to send per second. Unit: Count/s | DropPacketTX | instanceId, port, vip | Average, Minimum, Maximum | |
Listener health checks | Healthy backend ECS instances | The number of healthy backend ECS instances for the listener. Unit: Count | HeathyServerCount | instanceId, port, vip | Average, Minimum, Maximum |
Unhealthy backend ECS instances | The number of unhealthy backend ECS instances for the listener. Unit: Count | UnhealthyServerCount | instanceId, port, vip | Average, Minimum, Maximum |
Layer 7 protocol metrics
Metric type | Metric | Description | MetricName | Dimensions | Statistics |
Instance connections | Layer 7 RT (instance) | The time between a client sending a request and receiving a response from a backend server via the CLB instance. Unit: ms | InstanceRt | instanceId | Average |
Layer 7 Upstream RT (instance) | The time between the CLB instance forwarding a request and receiving a response from the backend server. Unit: ms | InstanceUpstreamRt | instanceId | Average | |
Instance requests | Layer 7 QPS (instance) | The number of HTTP or HTTPS requests that the CLB instance processes per second. Unit: Count/s | InstanceQps | instanceId | Average |
Instance status codes | Layer 7 2xx status codes (instance) | The number of 2xx success status codes returned per second from a backend server to a client through the CLB instance. Unit: Count/s | InstanceStatusCode2xx | instanceId | Average |
Layer 7 3xx status codes (instance) | The number of 3xx redirection status codes returned per second from a backend server to a client through the CLB instance. Unit: Count/s | InstanceStatusCode3xx | instanceId | Average | |
Layer 7 4xx status codes (instance) | The number of 4xx client error status codes returned per second from a backend server to a client through the CLB instance. Unit: Count/s | InstanceStatusCode4xx | instanceId | Average | |
Layer 7 5xx status codes (instance) | The number of 5xx server error status codes returned per second from a backend server to a client through the CLB instance. Unit: Count/s | InstanceStatusCode5xx | instanceId | Average | |
Layer 7 other status codes (instance) | The number of status codes other than 2xx, 3xx, 4xx, and 5xx returned per second from a backend server to a client through the CLB instance. Unit: Count/s | InstanceStatusCodeOther | instanceId | Average | |
Instance backend status codes | Layer 7 UpstreamCode4xx (instance) | The number of 4xx client error status codes returned per second from a backend server to the CLB instance. Unit: Count/s | InstanceUpstreamCode4xx | instanceId | Average |
Layer 7 UpstreamCode5xx (instance) | The number of 5xx server error status codes returned per second from a backend server to the CLB instance. Unit: Count/s | InstanceUpstreamCode5xx | instanceId | Average | |
Listener connections | Layer 7 RT (listener) | The time between a client sending a request and receiving a response from the backend server through the listener. Unit: ms | Rt | instanceId, port, vip | Average |
Layer 7 Upstream RT (listener) | The time between the CLB instance forwarding a request and receiving a response from the backend server through the listener. Unit: ms | UpstreamRt | instanceId, port, vip | Average | |
Listener requests | Layer 7 QPS (listener) | The number of HTTP or HTTPS requests that the listener processes per second. Unit: Count/s | Qps | instanceId, port, vip | Average |
Listener status codes | Layer 7 2xx status codes (listener) | The number of 2xx success status codes returned per second from a backend server to a client through the listener. Unit: Count/s | StatusCode2xx | instanceId, port, vip | Average |
Layer 7 3xx status codes (listener) | The number of 3xx redirection status codes returned per second from a backend server to a client through the listener. Unit: Count/s | StatusCode3xx | instanceId, port, vip | Average | |
Layer 7 4xx status codes (listener) | The number of 4xx client error status codes returned per second from a backend server to a client through the listener. Unit: Count/s | StatusCode4xx | instanceId, port, vip | Average | |
Layer 7 5xx status codes (listener) | The number of 5xx server error status codes returned per second from a backend server to a client through the listener. Unit: Count/s | StatusCode5xx | instanceId, port, vip | Average | |
Layer 7 other status codes (listener) | The number of status codes other than 2xx, 3xx, 4xx, and 5xx returned per second from a backend server to a client through the listener. Unit: Count/s | StatusCodeOther | instanceId, port, vip | Average | |
Listener backend status codes | Layer 7 UpstreamCode4xx (listener) | The number of 4xx client error status codes returned per second from a backend server to the CLB instance through the listener. Unit: Count/s | UpstreamCode4xx | instanceId, port, vip | Average |
Layer 7 UpstreamCode5xx (listener) | The number of 5xx server error status codes returned per second from a backend server to the CLB instance through the listener. Unit: Count/s | UpstreamCode5xx | instanceId, port, vip | Average |
Metrics available only by API and SDK
Layer 4 protocol metrics
Metric type | Metric | Description | MetricName | Dimensions | Statistics |
Instance connections | Connection utilization (instance) | The ratio of established connections to the maximum allowed connections for the CLB instance. Unit: % | InstanceMaxConnectionUtilization | instanceId | Average, Maximum, Minimum |
New connection utilization (instance) | The ratio of new connections to the maximum allowed new connections for the CLB instance. Unit: % | InstanceNewConnectionUtilization | instanceId | Average, Maximum, Minimum |
Layer 7 protocol metrics
Metric type | Metric | Description | MetricName | Dimensions | Statistics |
Instance requests | Layer 7 QPS utilization (instance) | The ratio of the actual QPS to the maximum QPS for the CLB instance. Unit: % | InstanceQpsUtilization | instanceId | Average, Maximum, Minimum |
FAQ
Monitoring data vs. billing data
Factor | Monitoring data | Billing data |
Calculation method | The load balancer system collects traffic data at a 1-minute sampling granularity and reports it to CloudMonitor. | Billing data is collected at the same sampling granularity. The load balancer system reports the hourly cumulative value to the billing system for invoicing. |
Timeliness | Monitoring data is provided in near real-time. However, small delays are inherent in the data collection, processing, and display pipeline. This can lead to minor discrepancies when compared with billing data. | The billing system is designed to accommodate processing delays of up to 3 hours. For example, usage data from the 01:00 to 02:00 hour, which is typically processed before 03:00, can be delayed and processed as late as 05:00. This intentional latency is a primary reason for differences between real-time monitoring data and final billing data. |
Purpose | Monitoring provides operational visibility into the real-time health and performance of an instance. Use this data to detect anomalies, diagnose issues, and trigger operational responses like alert rules. | Billing accurately calculates charges based on the actual resources consumed over a billing period. For all financial accounting and invoicing, billing data is the official source of truth, not monitoring data. |
References
To understand the differences between monitoring data and billing data, see Monitoring data and billing data.
To view monitoring data for CLB, see View CLB monitoring information.
To configure alert rules for a CLB instance, see Configure alert rules.