Alibaba Cloud Classic Load Balancer (CLB) Monitoring Integration
Site24x7 offers out-of-the-box monitoring support for Classic Load Balancers (CLB) in your Alibaba Cloud environment. By tracking traffic metrics, backend server status, and connection statistics, you can ensure efficient load distribution and detect performance issues in real time. Once you integrate your Alibaba account with Site24x7, all associated Classic Load Balancers are auto-discovered and monitored.
Use cases
- Traffic load distribution analysis: Monitor traffic patterns across front-end and back-end servers to identify imbalances, sudden traffic spikes, or uneven load distribution across zones.
- Backend instance health monitoring: Get alerted when backend ECS instances become unhealthy or unresponsive, ensuring quick failover and minimal downtime.
- Connection saturation detection: Track the number of concurrent connections to identify saturation issues that can lead to dropped connections or throttled performance.
- Latency troubleshooting: Analyze frontend and backend response times to detect latency issues caused by overloaded instances, slow DNS resolution, or misconfigured listeners.
- Resource planning and scaling: Use historical traffic and connection metrics to forecast load trends and make informed decisions about scaling backend resources.
- Security insight through connection patterns: Monitor unusual spikes in connections or requests that could indicate DDoS attempts or unauthorized access.
Setup and configuration
- Log in to your Site24x7 account and navigate to Cloud > Alibaba Cloud > Add Monitor.
- In the Edit Alibaba Cloud Monitor page, select Classic Load Balancer from the Service Types list.
- Once added, go to Cloud > Alibaba > Classic Load Balancer to view dashboards and performance metrics.
Supported metrics
HTTP Status Code Metrics
| Metric name | Description | Unit |
|---|---|---|
| Status Code Count (2xx) | The number of HTTP 2xx responses received by the load balancer. | Count |
| Status Code Count (3xx) | The number of HTTP 3xx responses received by the load balancer. | Count |
| Status Code Count (4xx) | The number of HTTP 4xx responses received by the load balancer. | Count |
| Status Code Count (5xx) | The number of HTTP 5xx responses received by the load balancer. | Count |
| Status Code Count (Other) | The number of HTTP responses outside the 2xx–5xx range. | Count |
| Instance Status Code Count (2xx) | The number of 2xx responses sent from backend instances. | Count |
| Instance Status Code Count (3xx) | The number of 3xx responses sent from backend instances. | Count |
| Instance Status Code Count (4xx) | The number of 4xx responses sent from backend instances. | Count |
| Instance Status Code Count (5xx) | The number of 5xx responses sent from backend instances. | Count |
| Instance Status Code Count (Other) | The number of other HTTP status codes from backend instances. | Count |
Upstream Response Metrics
| Metric name | Description | Unit |
|---|---|---|
| Upstream Status Code Count (4xx) | The number of 4xx responses returned from upstream servers. | Count |
| Upstream Status Code Count (5xx) | The number of 5xx responses returned from upstream servers. | Count |
| Instance Upstream Status Code Count (4xx) | The number of 4xx responses from upstream per instance. | Count |
| Instance Upstream Status Code Count (5xx) | The number of 5xx responses from upstream per instance. | Count |
| Upstream Response Time | The average response time from upstream servers. | Milliseconds |
| Instance Upstream Response Time | The average response time from upstream servers per instance. | Milliseconds |
Traffic Metrics
| Metric name | Description | Unit |
|---|---|---|
| Group Traffic Received | The amount of traffic received by the server group. | Bytes |
| Group Total Traffic Received | The total amount of traffic received by all instances in the group. | Bytes |
| Group Traffic Transmitted | The amount of traffic sent from the server group. | Bytes |
| Group Total Traffic Transmitted | The total amount of traffic sent from all instances in the group. | Bytes |
| New Traffic Received | The amount of incoming traffic from new connections. | Bytes |
| New Traffic Transmitted | The amount of outgoing traffic from new connections. | Bytes |
| Instance Traffic Received | The amount of traffic received by the instance. | Bytes |
| Instance Traffic Transmitted | The amount of traffic sent from the instance. | Bytes |
| Instance Traffic Utilization (Receive) | The percentage of allowed traffic capacity being received by the instance. | Percentage |
| Instance Traffic Utilization (Transmit) | The percentage of allowed traffic capacity being sent by the instance. | Percentage |
| Instance Dropped Traffic (Receive) | The amount of incoming traffic dropped by the instance. | Bytes |
| Instance Dropped Traffic (Transmit) | The amount of outgoing traffic dropped by the instance. | Bytes |
| Dropped Traffic (Receive) | The amount of inbound traffic dropped due to load balancer limits. | Bytes |
| Dropped Traffic (Transmit) | The amount of outbound traffic dropped due to load balancer limits. | Bytes |
Connection Metrics
| Metric name | Description | Unit |
|---|---|---|
| New Connection Count | The number of new connections established. | Count |
| Group New Connection Count | The number of new connections established in the server group. | Count |
| Instance New Connection Count | The number of new connections established on an instance. | Count |
| Instance New Connection Utilization | The percentage of maximum new connections utilized by the instance. | Percentage |
| Active Connection Count | The number of currently active connections. | Count |
| Group Active Connection Count | The number of active connections in the server group. | Count |
| Instance Active Connection Count | The number of active connections on the instance. | Count |
| Inactive Connection Count | The number of inactive connections at the load balancer. | Count |
| Instance Inactive Connection Count | The number of inactive connections on the backend instance. | Count |
| Dropped Connection Count | The number of connections dropped by the load balancer. | Count |
| Instance Dropped Connection Count | The number of connections dropped on the instance. | Count |
| Maximum Connection Count | The maximum number of connections allowed on the load balancer. | Count |
| Instance Maximum Connection Count | The maximum number of connections allowed on the instance. | Count |
| Instance Maximum Connection Utilization | The percentage of the connection capacity utilized by the instance. | Percentage |
Packet Metrics
| Metric name | Description | Unit |
|---|---|---|
| Packets Received | The number of packets received by the load balancer. | Count |
| Packets Transmitted | The number of packets sent by the load balancer. | Count |
| Instance Packets Received | The number of packets received by the instance. | Count |
| Instance Packets Transmitted | The number of packets sent from the instance. | Count |
| Dropped Packets (Receive) | The number of incoming packets dropped at the load balancer. | Count |
| Dropped Packets (Transmit) | The number of outgoing packets dropped at the load balancer. | Count |
| Instance Dropped Packets (Receive) | The number of incoming packets dropped by the instance. | Count |
| Instance Dropped Packets (Transmit) | The number of outgoing packets dropped by the instance. | Count |
Performance Metrics
| Metric name | Description | Unit |
|---|---|---|
| Queries Per Second (QPS) | The number of queries processed per second by the load balancer. | Count/second |
| Instance Queries Per Second (QPS) | The number of queries processed per second by the instance. | Count/second |
| Instance QPS Utilization | The percentage of the maximum QPS utilized by the instance. | Percentage |
| Response Time | The average response time recorded by the load balancer. | Milliseconds |
| Instance Response Time | The average response time recorded by the instance. | Milliseconds |
Health Metrics
| Metric name | Description | Unit |
|---|---|---|
| Healthy Server Count | The number of healthy backend servers. | Count |
| Unhealthy Server Count | The number of unhealthy backend servers. | Count |
| Healthy Server Count (With Rule) | The number of healthy servers based on health check rules. | Count |
| Unhealthy Server Count (With Rule) | The number of unhealthy servers based on health check rules. | Count |
| Group Unhealthy Server Count | The number of unhealthy servers in the group. | Count |
Threshold configuration
- Go to Admin > Configuration Profiles > Threshold and Availability.
- Create or edit a threshold profile for Classic Load Balancer.
- Assign the profile to the respective monitors to trigger alerts.
IT automation
Site24x7's IT Automation tools help with automatically resolving performance degradation issues. When a breach occurs, the alarm engine continuously examines the system events for which thresholds have been defined and performs the mapped automation.
- Go to Admin > IT Automation Templates.
- Create a new automation rule.
- Map the rule to the monitor for proactive resolution.
How to configure IT Automation for a monitor
Configuration rules
With Site24x7's Configuration Rules, you can set parameters like Threshold Profile, Notification Profile, Tags, and Monitor Group for multiple monitors and automate the configuration settings of your monitoring resources. Automatically assign these settings when new Classic Load Balancer monitors are added.
How to add a Configuration Rule