Alert Policies
You can create alert policies for instance metrics you care about, allowing Cloud Load Balance to promptly send alerts to the concerned user groups when the running status meets certain conditions. This ensures that you can quickly detect anomalies and take appropriate measures to maintain system stability and reliability. For more information, please refer to Alert Overview.
The alert policies for Cloud Load Balance include the following types:
Public Network Listener
Private Network Listener
Real Server
Listener level
Server port level
Server Port (Traditional Private Network)
Layer-7 Protocol Monitoring
Public/Private Network Listeners
Supported network listener metrics:
Metrics | Unit | Note |
Bandwidth in | Mbps | Bandwidth consumed when clients access the Cloud Load Balance through the public network within a sampling period. |
Outbound Bandwidth | Mbps | Bandwidth consumed by the Cloud Load Balance to access the public network within a sampling period. |
Inbound Packets | count/s | Number of request data packets received by the Cloud Load Balance per second within the statistical period. |
Outbound Packets | count/s | Number of data packets sent per second by Cloud Load Balance within a sampling period. |
Real Server
CLB supports alert policies on the listener and server port level.
1. Listener level
Set up a policy to trigger alerts when the number of abnormal ports of real servers bound to the listener reaches the threshold. In the example below, the number of abnormal ports of all real servers under the selected listener is collected once every minute. If the number is greater than 10 per second for two consecutive sampling periods, an alert is triggered. Only one alert is sent per day.
Note
Policy Type Selection:
Configure Trigger Conditions:
2. Server port level
You can configure a policy to receive alerts whenever a specified port of a real server bound to a listener is abnormal.
Policy Type Selection:
Configure Trigger Conditions:
Note
Real server port exception: The port of the real server is unavailable. Network jitter can also trigger port exceptions.
A listener-level policy is suggested as it covers ports of all bound real servers and is not affected by network jitter.
Server Port (Traditional Private Network)
You can configure server port exception alarms for private network Classic CLB as instructed in "Server Port (Other) > Server port level".
You can configure a policy to receive alerts whenever a specified port of a real server bound to a listener is abnormal.
Layer-7 Protocol Monitoring
For all Layer-7 listeners (HTTP/HTTPS), you can configure alert policies specific to Layer-7 monitoring metrics. The detailed metrics are as follows:
Metrics | <p> | Note |
Bandwidth in | Mbps | Bandwidth consumed when clients access the Cloud Load Balance through the public network within a sampling period. |
Outbound Bandwidth | Mbps | Bandwidth consumed by the Cloud Load Balance to access the public network within a sampling period. |
Inbound Packets | count/s | Number of request data packets received by Cloud Load Balance per second within a sampling period. |
Outbound Packets | count/s | Number of data packets sent per second by Cloud Load Balance within a sampling period. |
New connections | Connections | Number of new connections established per minute within a sampling period. |
Number of active connections | Connections | Number of active connections per minute within a sampling period. |
Average response time | ms | Average response time of CLB within a sampling period. |
Maximum response time | ms | Longest response time of CLB within a sampling period. |
2xx status codes | Connections | Number of 2xx status codes returned by the real server within a sampling period. |
3xx status codes | Connections | Number of 3xx status codes returned by the real server within a sampling period. |
4xx status codes | Connections | Number of 4xx status codes returned by the real server within a sampling period. |
5xx status codes | Connections | Number of 5xx status codes returned by the real server within a sampling period. |
404 status codes | Connections | Number of 404 status codes returned by the real server within a sampling period. |
502 status codes | Connections | Number of 502 status codes returned by real servers in the statistical period. |
3xx status codes returned by CLB | Connections | Number of 3xx status codes returned by Cloud Load Balance (CLB) within a sampling period. |
4xx status codes returned by CLB | Connections | Number of 4xx status codes returned by Cloud Load Balance (CLB) within a sampling period. |
5xx status codes returned by CLB | Connections | Number of 5xx status codes returned by Cloud Load Balance (CLB) within a sampling period. |
404 status codes returned by CLB | Connections | Number of 404 status codes returned by Cloud Load Balance (CLB) within a sampling period. |
502 status codes returned by CLB | Connections | Number of 502 status codes returned by Cloud Load Balance (CLB) within a sampling period. |