Cloud Virtual Machine
- Release Notes and Announcements
- Announcements
- Product Introduction
- Image
- Public Image
- TencentOS Server
- Network and Security
- OPS and Monitoring
- Purchase Guide
- Purchasing Instances
- Purchasing Cloud Disks
- Purchasing Reserved Instances
- Purchasing Public Network Bandwidth
- Getting Started
- Operation Guide
- Convenience Features
- Instances
- Creating Instances
- Logging In to Linux Instances
- Logging in to Windows instance
- Adjusting Configuration
- View Instance Details
- Managing Instance IPs
- Terminating/Returning Instances
- Reserved Instances
- Images
- Importing Images
- CentOS Linux Operations
- Migrating Servers
- Online Migration
- Migration Operation Guide
- Maintenance Tasks
- Networking
- Security
- Security Groups
- Managing Security Groups
- Managing Security Group Rules
- Monitoring and Alarms
- Practical Tutorial
- Building an Environment
- Setting up LNMP
- Setting up LAMP manually
- Setting up Java Web
- Setting up Node.js
- Manual Setup of WIPM Environment
- Building a Website
- Discuz! Forum
- Building an Application
- Setting Up FTP Site
- NTP Service
- Building a Visual GUI
- Uploading Local Files to CVM
- High-throughput Network Performance Test
- Operations Guide
- Initializing Data Disks
- Environment Configurations
- Installing Software
- Work with Operating Systems
- Troubleshooting
- Instance-Related Failures
- Windows Instance Login Failures
- Linux Instance Login Failures
- Linux CVM Memory Issues
- API Documentation
- Region APIs
- Instance APIs
- Cloud Hosting Cluster APIs
- Image APIs
- Instance Launch Template APIs
- Making API Requests
- Placement Group APIs
- Key APIs
- Security Group APIs
- Network APIs
- FAQs
- Billing
- Instance
- Storage
- Images
- OPS & Monitoring
- Related Agreement
Health Check
Last updated: 2024-01-08 09:12:28
Overview
Health check can check the status of performance, fees, network, and disk utilization of a CVM instance. With this feature, you can discover and solve instance problems promptly.
Use Cases
We recommend you use health check in the following two scenarios:
Troubleshooting: If any failure or problem occurs during instance operations, you can run a health check to locate and troubleshoot it.
All-around instance check: During daily Ops, health check can help you keep up to date with the overall instance running status.
Check Item Description
The health check items are as detailed below:
Local network
Check Item | Description | RiskLevel | Solution |
Network latency | An HTTP request is sent to check whether the network latency of the instance is high based on the following criteria: If the latency is above 600 ms, the network quality is considered poor. If no response is received within 5s, the request is considered timed out. If all requests time out, the network is considered disconnected. | Exception | Check your local network and solve the problem. |
| Network jitter | The average of the differences between the latency values of adjacent requests is the network jitter value. If the network jitter/latency is below or equal to 0.15, the network is stable; otherwise, the network is jittering. | - |
| Upstream bandwidth | Data packets are uploaded to the instance to calculate its upstream bandwidth. | - |
| Downstream bandwidth | Data packets are downloaded from the instance to calculate its downstream bandwidth. | - |
Security group
Check Item | Description | RiskLevel | Solution |
Common ports | Checks whether requests to common ports such as ports 22 and 3389 used by the TCP protocol for the inbound traffic are blocked in the security group. | Warning | If requests to port 22 used by the TCP protocol are blocked in an ingress rule in the security group, SSH login may be abnormal. You can open the required ports as instructed in Security Group Use Cases. |
Billing
Check Item | Description | RiskLevel | Solution |
Cloud disk status | Checks whether cloud disks associated with the instance have expired and whether they can be read/written. | Exception | A cloud disk associated with the instance has expired. Go to the CBS console to renew it as soon as possible. |
| Checks whether cloud disks associated with the pay-as-you-go instance are unavailable due to expiration. | Warning | Auto-Renewal is not enabled for the cloud disks attached to the instance. Go to the CBS console to configure auto-renewal for the cloud disk. |
| | ||
| |||
Instance storage
Check Item | Description | Risk Level | Solution |
High cloud disk latency | Checks whether the I/O performance metric svctm is abnormal. | Warning | A cloud disk associated with the instance has a high latency. We recommend you pay attention to the cloud disk usage. |
Cloud disk I/O | Checks for cloud disk I/O hang | Warning | A cloud disk associated with the instance has an I/O hang. We recommend you pay attention to the cloud disk usage. |
System disk inode utilization | Checks whether the inode utilization of the cloud disk has reached 100%. | Warning | |
System disk read-only | Checks whether the cloud disk is read-only. | Exception | |
System disk space utilization | Checks whether the utilization of the cloud disk has reached 100%. | Warning | |
Partition I/O utilization | Checks whether the io_util of the cloud disk has reached 100%. | Warning | |
Instance status
Check Item | Description | RiskLevel | Solution |
Instance shutdown | Checks whether the instance is shut down. | Warning | |
Instance restart history | Checks whether the instance has been restarted in the last 12 hours. | Warning | The instance has been restarted in the last 12 hours. Pay attention to the instance running status. |
Instance kernel crash | Checks whether a hung task has occurred in the instance in the last 12 hours. | Exception | A hung task, panic, or soft deadlock has occurred in the instance in the last 12 hours. Pay attention to the instance running status and troubleshoot as instructed in Kernel and I/O Issues. |
| | Checks whether a panic has occurred in the instance in the last 12 hours. | Exception |
| | Checks whether a soft deadlock occurred in the instance in the last 12 hours. | Exception |
Instance performance
Check Item | Description | RiskLevel | Solution |
CPU utilization | Checks whether the instance has experienced a high CPU utilization in the last 12 hours. | Warning | Check your CPU utilization and adjust the configuration according. Troubleshoot it as instructed below: Windows instance: Login Failure Due To High CPU and Memory Usage (Windows) Linux instance: Login Failure Due To High CPU and Memory Usage (Linux) |
| Memory utilization | Checks whether the instance has experienced a high memory utilization in the last 12 hours. | Warning |
| Basic CPU utilization | Checks whether the instance has experienced a high CPU utilization in the last 12 hours. | Warning |
Instance network
Check Item | Description | RiskLevel | Solution |
Public EIP connection | Checks whether the EIP is isolated due to overdue payments. | Exception | An EIP may be disconnected from the public network due to overdue payments. You need to go to the Billing Center to make the overdue payment. |
Existence of EIP | Checks whether the instance has an EIP. | Warning | The instance has no EIPs. If you want to use an EIP to access the public network, go to the EIP console to bind one. |
EIP blocked | Checks whether the EIP is blocked due to DDoS attacks | Exception | An instance EIP is blocked due to DDoS attacks. |
Public network bandwidth utilization | Checks whether the instance has experienced a high public network inbound bandwidth utilization in the last 12 hours. | Warning | Check the network usage and troubleshoot as instructed in Login Failure Due to High Bandwidth Utilization. |
| | Checks whether the instance has experienced a high public network outbound bandwidth utilization in the last 12 hours. | Warning |
| Private network bandwidth utilization | Checks whether the instance has experienced a high private network inbound bandwidth utilization in the last 12 hours. | Warning |
| | Checks whether the instance has experienced a high private network outbound bandwidth utilization in the last 12 hours. | Warning |
Packet loss | Checks whether the instance has experienced TCP packet loss due to triggering of traffic throttling in the last 12 hours. | Warning | |
| | Checks whether the instance has experienced UDP packet loss due to triggering of traffic throttling in the last 12 hours. | Warning |
| | Checks whether the instance has experienced packet loss due to a soft interrupt in the last 12 hours. | Warning |
| Kernel network conditions | Checks whether the instance has experienced a full UDP send buffer in the last 12 hours. | Warning |
| | Checks whether the instance has experienced a full UDP receive buffer in the last 12 hours. | Warning |
| | Checks whether the instance has experienced a full TCP complete connection queue in the last 12 hours. | Warning |
| | Checks whether the instance has experienced TCP request overflow in the last 12 hours. | Warning |
| Connection utilization | Checks whether the number of connections of the instance has reached the upper limit in the last 12 hours. | Warning |
Related Operations
You can generate an instance detection result report or view historical reports as instructed in Checking Instance Status.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No