Common Causes and Solutions for Monitoring Components Going Offline

Offline criteria for monitoring components:

When the monitoring component of a CVM fails to report data for 5 consecutive minutes, the platform considers the monitoring component of this CVM to be offline.

The following are the top causes for monitoring components going offline and the corresponding troubleshooting methods.

1. User Operations on the CVM Through the Console or Command Line

When a CVM is shut down through operations, it enters a shutdown status, causing the monitoring component to go offline and no data available.

When users operate through the CVM console or log into the CVM to perform common CVM Ops such as restarting, upgrading the CVM, reinstalling, or creating images, it will result in a timeout in CVM monitoring data reporting, causing the monitoring component to go offline.

Troubleshooting method: You can check whether there are relevant Ops on the CVM based on the specific time point. You can also view operation logs by clicking Operation Log on the CVM Details page.

2. High Load on the CVM

High CPU load, full memory, and full bandwidth on CVM can all lead to abnormal data reporting by the monitoring component.

Troubleshooting method: You can log in to the CVM or view the monitoring views to check whether CPU, memory, and bandwidth utilization reach 100%. If so, you can scale out the CVM based on the actual situation.

3. Configuration Error of CVM's Private DNS

The configuration error of CVM's private DNS will prevent the monitoring component from reporting data.

Troubleshooting method: For private DNS configuration of the Cloud Platform, see Private DNS Access and Configuration.