Load Balancer
Load Balancer
Load Balancer
Document
Announcement
Network Load Balancer (NLB)
What's New
Product Description
Quick Start
User Guide
NLB instances
Server Group
Listeners
Projects and Tags
Best Practices
Cross-VPC Backend Server
API
NLB Instance
Listener
Server group
TLS Security Policy
SDK Reference
Application Load Balancer (ALB)
Updates and Announcements
Overview
Getting Started
User Guide
Instance
Listeners
Creating a listener
Forwarding rules
Server groups
Manage certificates
Security management
Logs and monitoring
Application of ALB in VKE
Resource management
Project-based management
Tag-based management
API Reference
ALB Instance
Availability Zone
Listener
server group
Health Check Template
forwarding rules
certificate
access log interface
Health Check Log
access control
personalized configuration
Best Practices
FAQs
Classic Load Balancer (CLB)
Overview
Product billing
Quick Start
User Guide
CLB instances
Backend Server Group
Listener
Creating a listener
Configuring a forwarding rule
Certificate management
Logs and monitoring
Identity and Access Management
Projects and Tags
Best Practices
Creating a static page
Configuration practice of a forwarding rule
Disaster Recovery Best Practices
Obtaining the client source IP address
API reference
CLB instances
Listener
Backend server group
ACL
Forwarding rule
Certificate
Access log (Layer-7)
Health check log
SDK Reference
- Documentation
Load BalancerClassic Load Balancer (CLB)User GuideHealth checkViewing the health check status
Copy page
Download PDFHealth check
Viewing the health check status
Copy pageDownload PDFViewing the health check status
Procedures
- Log in to the CLB console.
- In the top menu bar, select the target project and region.
- In the CLB instance list, you can see the number of listeners with health check exceptions.
- Click the CLB instance name to go to the Listener tab.
- In the Health Check Status column, click the Abnormal tag to view the details of the abnormal backend servers.
- Based on the prompt, you can learn the number of abnormal servers and preliminary troubleshooting methods. For detailed steps, see Configuring a backend server security group and Configuring a secondary network interface route.
- Click the server name to navigate to the ECS instance details page for detailed information.
- If the listener uses a Layer 7 protocol, you can also view the number of forwarding rules associated with the faulty backend server group.
tip
While viewing, health check status updates may display with a delay, which requires to manually refresh the page to view the latest status.
- (Optional) If you need to temporarily remove a faulty server, see Removing a backend server.
Related documents
Last updated: 2026.06.17 14:29:35
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
