Alarm Description
You can create alarms for instance metrics that you are interested in, so that when the running status of the CLB instance reaches a certain condition, alarm information can be sent to the user groups that are interested in it in a timely manner. This ensures that you can detect exceptional conditions in a timely manner and take appropriate measures to maintain the stability and reliability of the system. For details, see Alarm Overview.
The CLB alarm policies include the following types:
- Public network listener
- Private network listener
- Server port
- Server port dimension
Public Network Monitor/Private Network Listener
Currently, both public network CLB and private network CLB support alarms at the listener dimension. The specific metrics are as follows:
| Metrics | Unit | Note |
|---|---|---|
| Inbound Bandwidth | bps | The bandwidth used by clients to access the CLB function through the public network during the statistical period. |
| Outbound Bandwidth | bps | The bandwidth used by CLB to access the public network during the statistical period. |
| Number of packages | per second | The number of request data packets received by the private CLB per second during the statistical period. |
| Number of outgoing packets | per second | The number of data packets sent by the CLB per second during the statistical period. |
Server port
CLB supports alarms at the server port dimension:
You can configure an abnormal alarm for a port of a backend CVM bound to a listener, and send an alarm as long as the port is exceptional.
Alarm object configuration:
Trigger condition configuration:
Note:
The backend server port exception means: the CLB detects that the port of the backend server is unavailable. A few network jitters can also trigger port exceptions.