Overview
The self-service instance detection can detect the performance, cost, network, disk, and other statuses of CVM instances, and help you understand the running status of the instances.
This feature allows you to promptly discover and resolve instance-related issues.
Application Scenario
The earlier two scenarios recommend using self-service instance detection:
- Troubleshooting: If you encounter a fault or problem during instance operation, you can use self-service instance detection to troubleshoot and locate the problem, and handle the exceptions according to the corresponding suggestions.
- Comprehensive instance detection: During daily Ops, you can use self-service instance detection to understand the overall operation status of the instance, discover and solve problems on time, and ensure the normal operation of the business.
Detection Item Description
Account Fee Detection
| Detection Items | Detection Description | Solution |
|---|---|---|
| Whether the CBS has expired and whether the expiration time of the instance and the CBS is consistent | Whether the CBS associated with the instance has expired or cannot be read or written to | The CBS of this instance has expired. Proceed to the CBS console to renew your subscription as soon as possible. |
| Whether the CBS has expired and whether the expiration time of the instance and the CBS is consistent | Whether the instance becomes unusable due to the expiration of the CBS | The CBS of this instance is not set to automatically renew. The cloud disk may expire and become unavailable. It is recommended to proceed to the CBS console to set up CBS renewal. |
Instance Storage Detection
| Detection Items | Detection Description | Solution |
|---|---|---|
| Has there been an IO HANG issue with the CBS | Has there been an IO HANG issue with the CBS | The CBS of this instance has an IO HANG issue. It is recommended that you pay attention to the usage of the CBS. |
| CBS Space Usage Detection | Has the disk usage of the CBS reached 100%? | It is recommended that you pay attention to the usage of the CBS |
| CBS io_util Detection | Has the io_util of the CBS reached 100%? | It is recommended that you pay attention to the usage of the CBS |
| Is the CBS in read-only mode | Is the CBS currently in read-only status | It is recommended that you pay attention to the usage of the CBS |
| Detection of CBS iNode Usage | Has the iNode usage of the CBS reached 100%? | It is recommended that you pay attention to the usage of the CBS |
| Is the CBS experiencing a high delay | Is the IO performance svctm metric abnormal | The CBS of this instance has a high delay problem. It is recommended that you pay attention to the usage of the CBS. |
Instance Performance Detection
| Detection Items | Detection Description | Solution |
|---|---|---|
| Memory Usage | Has the instance experienced excessive memory load within the last 12 hours | To avoid becoming a service bottleneck, we recommend that you check CPU usage and adjust the configuration on time. |
| Basic CPU Usage | Has the instance experienced a high CPU load in the last 12 hours? | Same as above |
| CPU Usage | Has the instance experienced a high CPU load in the last 12 hours? | Same as above |
Instance Status Detection
| Detection Items | Detection Description | Solution |
|---|---|---|
| Has the instance experienced a kernel fault? | - Has the instance experienced a hungtask in the last 12 hours? - Has the instance experienced a panic in the last 12 hours? - Has the instance experienced a soft deadlock in the last 12 hours? |
The instance has experienced hungtask/panic/soft deadlock in the last 12 hours. Please pay attention to the instance running status. |
| Whether the instance was restarted? | Whether the instance was restarted in the last 12 hours? | The instance has been restarted in the last 12 hours. Pay attention to the instance status. |
| Instance Shutdown Status Detection | Is the instance currently shut down? | The instance is shut down. You can go to the CVM console to start it up. |
Instance Network Monitoring
| Detection Items | Detection Description | Solution |
|---|---|---|
| Is the instance's public IP blocked by DDOS? | Is the public IP blocked by DDOS? | The public IP address of this instance was blocked due to DDOS attack. |
| Does it have a public IP? | Does the instance have a public IP? | This instance does not have a public IP. If you need a public network IP for external access, you can go to the Elastic IP console to bind an EIP. |
| Is the public IP disconnected due to overdue payment? | Is the public IP isolated due to overdue payment? | The public IP may be unable to communicate with the external network due to overdue payment. We recommend you to recharge your account as soon as possible. |
| Detection of Public Network Bandwidth Utilization | - Whether the instance has experienced excessively high public network inbound bandwidth in the last 12 hours? - Whether the instance has experienced excessively high public network outbound bandwidth in the last 12 hours? |
To avoid becoming a business bottleneck, we recommend that you check the network usage. |
| Kernel Network Detection | - Whether the instance has experienced a UDP send buffer full within the last 12 hours? - Whether the instance has experienced a UDP receive buffer full within the last 12 hours? - Whether the instance has experienced a full TCP accept queue within the last 12 hours? - Whether the instance has experienced TCP request overflow within the last 12 hours? |
To avoid becoming a business bottleneck, we recommend that you check the health of your business. |
| Whether the number of connections has reached the upper limit? | Whether the instance has reached the upper limit of the number of connections within the last 12 hours? | To avoid becoming a business bottleneck, we recommend that you check the health of your business. |