tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary
DocumentationCloud Load BalancerOperation GuideMonitoring and AlarmAlarming Metric Descriptions

Alarming Metric Descriptions

PDF
Focus Mode
Font Size
Last updated: 2025-12-26 17:58:23

Basic Description

You can create alarm policies for your followed instance metrics, enabling to promptly send alarms to the concerned user groups when a CLB instance meets a certain condition during operation. This ensures you can detect abnormalities in time and take appropriate measures to maintain the stability and reliability of the system. For more information, see Alarm Overview. For best practices on configuring the alarm policies, see Best Practice for Configuring Monitoring Alarm Policies of CLB.
The alarm policies of CLB include the following types:
Public network CLB instance
Private network CLB instance
Layer 7 listener
Layer 4 listener

Description of Alarm Policies for Instances

Alarm Policy Type
Alarm Policy
Alarm Metric
Unit
Public network CLB instance
Client-to-LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
LB-to-backend monitoring
Public network outbound traffic
MB
Public network new connections
Count/s
Public network connections
Count
Public network outbound bandwidth
Mbps
Public network inbound bandwidth
Mbps
Public network outbound packets
Count/s
Public network inbound packets
Count/s
QPS-related monitoring
Number of requests per second
Count/s
QPS utilization
%
Discarded QPS
Count/s
Discard/Utilization monitoring
Utilization of new connections
%
Utilization of concurrent connections
%
Outbound bandwidth utilization
%
Inbound bandwidth utilization
%
Discarded outbound bandwidth
Bit/s
Discarded inbound bandwidth
Bit/s
Discarded connections
Count/s
Discarded outbound packets
Count/s
Discarded inbound packets
Count/s
Private network CLB instance
Client-to-LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
LB-to-backend monitoring
Inbound bandwidth
Mbps
Outbound bandwidth
Mbps
QPS-related monitoring
Number of requests per second
Count/s
QPS utilization
Count/s
Discarded QPS
%
Discard/Utilization monitoring
Utilization of new connections
%
Utilization of concurrent connections
%
Outbound bandwidth utilization
%
Inbound bandwidth utilization
%
Discarded outbound bandwidth
Bit/s
Discarded inbound bandwidth
Bit/s
Discarded connections
Count/s
Discarded outbound packets
Count/s
Discarded inbound packets
Count/s

Description of Alarm Policies for Listeners

Alarm Policy Type
Alarm Policy
Alarm Metric
Unit
Layer 4 listener
Client-to-private network LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
Private network LB-to-backend monitoring
Inbound packets
Count/s
Outbound packets
Count/s
Inbound bandwidth
Mbps
Outbound bandwidth
Mbps
New connections
Count/min
Concurrent connections
Count
Client-to-public network LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
Public network LB-to-backend monitoring
Inbound packets
Count/s
Outbound packets
Count/s
Inbound bandwidth
Mbps
Outbound bandwidth
Mbps
Public network connections
Count
New connections
Count/s
Inactive connections
Count
Layer 7 listener
Client-to-private network LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
Private network LB-to-backend monitoring
Status code of 2xx returned from CLB
Count/min
Status code of 3xx returned from CLB
Count/min
Status code of 4xx returned from CLB
Count/min
Status code of 5xx returned from CLB
Count/min
Status code of 404 returned from CLB
Count/min
Status code of 499 returned from CLB
Count/min
Status code of 502 returned from CLB
Count/min
Status code of 503 returned from CLB
Count/min
Status code of 504 returned from CLB
Count/min
Other status codes
Count/min
Status code of 2xx
Count/min
Status code of 3xx
Count/min
Status code of 4xx
Count/min
Status code of 5xx
Count/min
Status code of 404
Count/min
Status code of 499
Count/min
Status code of 502
Count/min
Status code of 503
Count/min
Status code of 504
Count/min
Average response time
ms
Maximum response time
ms
Average request time
ms
Number of response timeouts
Count/min
Maximum request latency
ms
Number of requests per second
Count/s
Number of successful requests per minute
Count/min
Discarded QPS
Count/s
Client-to-public network LB monitoring
Client-to-LB outbound bandwidth
Mbps
Client-to-LB inbound bandwidth
Mbps
Client-to-LB connections
Count
Client-to-LB inactive connections
Count
Client-to-LB concurrent connections
Count
Client-to-LB new connections
Count/s
Client-to-LB inbound packets
Count/s
Client-to-LB outbound packets
Count/s
Public network LB-to-backend monitoring
Status code of 2xx returned from CLB
Count/min
Status code of 3xx returned from CLB
Count/min
Status code of 4xx returned from CLB
Count/min
Status code of 5xx returned from CLB
Count/min
Status code of 404 returned from CLB
Count/min
Status code of 499 returned from CLB
Count/min
Status code of 502 returned from CLB
Count/min
Status code of 503 returned from CLB
Count/min
Status code of 504 returned from CLB
Count/min
Other status codes
Count/min
Status code of 2xx
Count/min
Status code of 3xx
Count/min
Status code of 4xx
Count/min
Status code of 5xx
Count/min
Status code of 404
Count/min
Status code of 499
Count/min
Status code of 502
Count/min
Status code of 503
Count/min
Status code of 504
Count/min
Average response time
ms
Maximum response time
ms
Average request time
ms
Number of response timeouts
Count/min
Maximum request time
ms
Number of requests per second
Count/s
Active connections
Count
New connections
Count/min
Inbound packets
Count/s
Outbound packets
Count/s
Outbound bandwidth
bps
Inbound bandwidth
bps

Health Check Alarm Policy Description

Alarm Policy Type
Alarm Policy
Alarm Metric
Unit
Health Check Monitoring
Listener
Number of abnormal RS in health check
Count
Number of normal RS in health check
Count
Backend server port
Backend server port
Number of abnormal server ports
Count
Note:
Abnormal health check status means that: CLB detected that this port of the backend server is unavailable. A few cases of network jitter will also trigger port anomaly.
The statistics of the listener include the port status of all backend services under this listener. To converge from a single alarm to a threshold alarm and reduce the impact of network jitter, it is recommended to use the alarms of listeners.

Previous Topic: Configuring Alarm PolicyNext Topic: Overview

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback