The possible causes are as follows:
To troubleshoot, please see CVM Has No Monitoring Data.
If the private DNS of the CVM is incorrectly configured, the Agent will fail to be downloaded and monitoring components will fail to report data. For more information about the private DNS configurations of CVMs, please see Private Network Access.
The installation on Windows is automatic. The installer automatically exits after installation. If you want to view the prompt during installation, run the installer in CLI mode.
After the installation is complete, the sgagent process will start first, followed by the barad_agent process to be launched within 5 minutes. Before installation, check whether the disk partition where the installation directory resides is full, whether inode is full, whether the write permission has been granted, and whether the network is normal.
If the network is normal, users can view the monitoring data at the frontend 5 minutes after the barad_agent process is started.
Run the uninstallation script in the
admin sub-directory under the Agent installation directory to automatically uninstall Agent.
/usr/local/qcloud/monitor/barad/admindirectory, run the stop.sh script to stop Agent, and then run the trystart.sh script to start Agent.
If you see a yellow exclamation mark (!) on the monitoring list page in Cloud Monitor > Cloud Product Monitor > Cloud Virtual Machine, log in to the CVM instance and check whether the Agent is running properly. If so, the reported failure may be caused by a network error, which stops the backend from detecting the Agent status of the CVM. In this case, you can enable the firewall. If the problem persists, submit a ticket to contact us for troubleshooting.
You can troubleshoot by referring to CVM Has No Monitoring Data.