You can determine whether Agent is offline based on the following conditions:
If the Agent on a Cloud Virtual Machine (CVM) instance does not report any data for five minutes, the platform considers Agent to be offline.
The top reasons why Agent goes offline and corresponding troubleshooting methods are described as follows:
After the CVM is shut down, Agent on the instance goes offline and no data will be reported.
When you perform any CVM OPS such as restart, upgrade, reinstallation, or image creation in the CVM console or after logging in to the CVM, the reporting of CVM monitoring data may time out and Agent will be taken offline.
Troubleshooting: You can access the CVM details page and view operation logs to determine whether any relevant operations were performed on the CVM at that time.
If the CVM CPU has a high load and the memory or bandwidth is used up, Agent may fail to report data.
Troubleshooting Method: You can log in to the CVM or check the monitoring view to determine whether the CPU, memory, or bandwidth is fully utilized. If yes, expand the service as needed.
If the private DNS configuration of the CVM is incorrect, Agent may fail to report data.
Troubleshooting: for more information on private network DNS configuration, see Private Network Access.
wget http://update2.agent.tencentyun.com/&& chmod + monitor_agent_admin/monitor_agent_admin
sh ./monitor_agent_admin check
wget http://update2.agent.tencentyun.com/update/monitor_agent_admin && chmod +x monitor_agent_admin
- Log path for Windows: C:\Program Files\QCloud\Monitor\Barad\logs\info.log
- Each log contains "nws send succ".
/usr/local/qcloud/monitor/barad/log/executor.loglog file contains any errors.
nws_urlin the plugin.ini file under the etc directory.
nws send faildoes not appear during reporting, perform the following operations:
In Linux: /etc/uuid In Windows: C:\windows\system32\drivers\etc\uuid The latest file named in uuid format in the C:\windows\system32\drivers\etc\ directory
/usr/sbin/ntpdate ntpupdate.tencentyun.comcommand to check whether the time change is 50 seconds or less. If the time change exceeds 50 seconds, restart barad_agent..