What Should I Do If the Agent Status Is Running But Monitoring Data Is Missing?
Symptom
System Time Jump
The collection time of the Cloud Eye Agent is subject to the OS time of the ECS. If the system clock jumps discontinuously and sharply (forward or backward) within a short period of time, instead of changing smoothly, it may appear that data points are lost (time changes due to time synchronization). However, the collection points are not lost.
Large Difference Between the Server Time and Actual Time
When the Agent reports data, it uses the ECS or BMS local time. When the console delivers requests, it uses the browser time of the user client. If the two times are different, no OS monitoring data will be displayed on the Cloud Eye console. For details about how to rectify the fault, see Does Huawei Cloud Provide the NTP Server and How Can I Configure It?
Server Network Exception
- If the Restore Agent Configurations button is displayed above the server list on the Server Monitoring page, the page is of the earlier version. The earlier version page supports only the installation of the earlier version Agent. For details, see Agent of the Earlier Version.
- If the Restore Agent Configurations button is not displayed, the page is of the new version. Check the current Agent version by referring to Checking the Cloud Eye Agent Version. If the Agent is of the earlier version, upgrade it to the new version by referring to Upgrading the Agent. If the fault persists, see Agent of the New Version for troubleshooting.
- Log in to the server and obtain the endpoint from the Agent configuration file.
- For Linux, run the following command:
cat /usr/local/telescope/bin/conf_ces.json
- For Windows, open the bin/conf_ces.json configuration file in the directory where the Agent installation package is stored.
- For Linux, run the following command:
- Check whether the endpoint in the Agent configuration file is the same as that of the current region. For details about Cloud Eye endpoints for each region, see Regions and Endpoints.
The following uses CN North-Beijing4 as an example to describe the endpoint in the conf_ces.json configuration file.
{"Endpoint":"https://ces.cn-north-4.myhuaweicloud.com"}- If yes, go to the next step.
- If no, modify the endpoint in the configuration file.
- Run the following command to check whether the DNS resolution is normal:
ping {Endpoint}Take CN North-Beijing4 as an example. The command is as follows:ping ces.cn-north-4.myhuaweicloud.com
- If a message is displayed indicating that the network is abnormal, check and modify the DNS configuration by referring to Checking/Modifying the DNS and Security Group Configurations.
- Run the following command to check whether the DNS resolution is normal:
ping agent.ces.myhuaweicloud.com
- If a message is displayed indicating that the network is abnormal, check and modify the DNS configuration by referring to Checking/Modifying the DNS and Security Group Configurations.
High Agent Load
For the Agent of the new version, when the Agent load is too high, the circuit breaker mechanism may be triggered. After the circuit breaker is triggered, the system stops collecting server metrics and attempts to restart the Agent within 5 minutes. As a result, monitoring data may be missing. For more information, see What Is the Circuit Breaker Mechanism of the Agent? To locate and rectify the fault, perform the following steps:
- Log in to the server.
- Check whether the ces.log file contains information about high Agent load. If no, go to step 3. If yes, go to step 4.
- For Linux, run the following command:
grep "Agent will exit due to fuse protection" /usr/local/uniagent/extension/install/telescope/log/ces.log
- For Windows, open the ces.log file and search for "Agent will exit due to fuse protection". The log path is as follows:
"C:\Program Files\uniagent\extension\install\telescope\log"
- For Linux, run the following command:
- Check whether the uniagent.log file contains information about high Agent load. If no, the Agent load is normal. If yes, go to step 4.
- For Linux, run the following command:
grep "telescope has occurred for 3 times" /usr/local/uniagent/log/uniagent.log
- For Windows, open the ces.log file and search for "telescope has occurred for 3 times". The log path is as follows:
"C:\Program Files\uniagent\log"
- For Linux, run the following command:
- Increase the Agent resource usage threshold by referring to How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?
Abnormal Agent Process
- Check the Agent version installed on the server. For details, see Checking the Cloud Eye Agent Version.
- Log in to the server and check whether the Agent process is running properly. For details, see Checking the Agent Status.
ps -ef |grep telescope
- If the Agent is abnormal, start the Agent by referring to Starting the Agent.
Abnormal Agent Agency
- If the Restore Agent Configurations button is displayed above the server list on the Server Monitoring page, the page is of the earlier version. The earlier version page supports only the installation of the earlier version Agent. For details, see Agent of the Earlier Version.
- If the Restore Agent Configurations button is not displayed, the page is of the new version. Check the Agent version of the server by referring to Checking the Cloud Eye Agent Version. If the Agent is of the earlier version, upgrade it to the new version. If the fault persists, see Agent of the New Version for troubleshooting.
- Check whether the cloud server agency has been created.
- Linux: Log in to the server and run the following command. If the command fails to be executed or the command output shown in Figure 2 is displayed, the agency is abnormal.
curl http://169.254.169.254/openstack/latest/securitykey
- Windows: Access the following address. If the access fails, the agency is abnormal.
http://169.254.169.254/openstack/latest/meta_data.json
- Linux: Log in to the server and run the following command. If the command fails to be executed or the command output shown in Figure 2 is displayed, the agency is abnormal.
- Go to the Server Monitoring page, select the target server, and click Restore Agent Configurations above the list.
- Check whether the cloud server agency has been created.
- Linux: Log in to the server and run the following command. If the command fails to be executed or the command output shown in Figure 3 is displayed, the agency is abnormal.
curl -ivk https://agent.ces.myhuaweicloud.com/v1.0/agencies/cesagency/securitykey
- Windows
Log in to the IAM console, choose Agencies, and search for cesagency. Click the agency name. In the Permissions area, check whether the value of Project [Region] of the CES AgentAccess permission contains the current region. If the current region is not contained, the agency is abnormal.
- Linux: Log in to the server and run the following command. If the command fails to be executed or the command output shown in Figure 3 is displayed, the agency is abnormal.
- Log in to the IAM console, choose Agencies, and search for the cesagency agency.
- Locate the row that contains cesagency and click Authorize in the Operation column.
- On the Authorize Agency page, search for and select CES Administrator, and click Next.
- Configure the authorization scope and click OK.
Abnormal Route Configuration
- Run the following command to check the route:
- Linux
route -n
If the following information is displayed, the route is normal.
Figure 4 Normal route configuration (Linux)
- Windows
route print
If the following information is displayed, the route is normal:
Figure 5 Normal route configuration (Windows)
- Linux
- If the route does not exist, run the following command to add a route:
- Linux
route add -host 169.254.169.254 gw 192.168.0.1
- Windows
route add 169.254.169.254 mask 255.255.255.255 192.168.0.1
Replace 192.168.0.1 in the example command with the gateway of the server.
- Linux
Incorrect InstanceId Configuration in the conf File
If there is no monitoring data 10 minutes after the Agent is installed, InstanceId in the conf file may be incorrectly configured.
Check whether the configuration is correct by referring to (Optional) Manually Configuring the Agent in the Cloud Eye User Guide.
Submitting a Service Ticket
If the problem persists, submit a service ticket.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot


