tencent cloud

Feedback

CVM Has No Monitoring Data

Last updated: 2022-08-25 18:07:30

    Overview

    The CVM instance must have the monitoring component agents installed to collect CVM metric data. If you cannot get the monitoring metric data, refer to this document to troubleshoot this problem.
    We recommend you reinstall the agents first as instructed in Installing CVM Agents and wait 3 minutes before checking again whether the monitoring data is restored. If an error occurs during the reinstallation or the monitoring data is not restored, troubleshoot the problem as detailed below.

    Causes and Solutions

    Cause Solution
    The agents are not installed/started Troubleshoot by referring to Step 1
    The reporting domains cannot be resolved Troubleshoot by referring to Step 2
    The agents failed to get the UUID Troubleshoot by referring to Step 3
    The CVM instance is shut down or being restarted Troubleshoot by referring to Step 4
    The CVM instance is under high load Troubleshoot by referring to Step 5

    Troubleshooting Procedure

    Step 1. Check whether the agents have been installed or started

    The troubleshooting procedures for Linux and Windows are different. You can refer to a procedure as needed.

    1. Run the following command to check whether the agents have been installed successfully.

    crontab -l |grep stargate
    

    If the following message is displayed, the agents have been installed:

    If not, install the agents as instructed in Installing CVM Agents.

    2. Check whether the agents run properly.
    Run the following commands to check whether the agents run properly:

    ps ax | grep sgagent
    ps ax | grep barad_agent
    

    If the output is as shown below, the agents run normally (note that the number of barad_agent processes is 3):


    If there is no output or the number of processes is incorrect, the agents are abnormal. In this case, run the following commands as the root account to start the agents. If the messages stargate agent run succ and barad_agent run succ are displayed, the agents have been restarted successfully.

    cd /usr/local/qcloud/stargate/admin
    ./restart.sh
    cd /usr/local/qcloud/monitor/barad/admin
    ./stop.sh
    ./trystart.sh
    

    > ?After the agents are started, wait 3 minutes and then check whether there is monitoring data in the CVM console.

    Step 2. Check reporting domains

    The following 4 domains need to be resolved for the agents to run properly:

    • update2.agent.tencentyun.com
    • receiver.barad.tencentyun.com
    • custom.message.tencentyun.com
    • metadata.tencentyun.com

    The procedures for checking and fixing the reporting domains are different for Linux and Windows. You can refer to a procedure as needed.

    1. Check whether the reporting domains can be resolved properly.
    Run the following commands to check whether these 4 domains can be resolved properly:

    ping -c 1 update2.agent.tencentyun.com
    ping -c 1 receiver.barad.tencentyun.com
    ping -c 1 custom.message.tencentyun.com
    ping -c 1 metadata.tencentyun.com 
    

    In normal cases, these 4 domains can be resolved on the CVM instance. If unknown host is displayed, the domains fail to be resolved. You can proceed to the next step to fix it.

    2. Fix DNS resolution.
    Tencent Cloud provides reliable private network DNS servers in different regions. We recommend you not overwrite the default DNS configurations. If you need to modify them, fix the resolution for the 4 domains above as follows:

    1. If you use a self-built/third-party DNS service, we recommend you not add the private network DNS provided by Tencent Cloud in /etc/resolv.conf. For more information, see Private Network Access.
    2. If you use a self-built DNS service, you can also add the 4 domains above to your DNS. The domain and IP mappings are as follows:
      Domain NameIP
      update2.agent.tencentyun.com169.254.0.15
      receiver.barad.tencentyun.com169.254.0.4
      custom.message.tencentyun.com169.254.0.5
      metadata.tencentyun.com 169.254.10.10
    3. If the two methods above cannot work, you can add the following configuration to the `/etc/hosts` file on the server:

    169.254.0.15 update2.agent.tencentyun.com
    169.254.0.4 receiver.barad.tencentyun.com
    169.254.0.5 custom.message.tencentyun.com
    169.254.10.10 metadata.tencentyun.com 
    

    > ?After the domain resolution issue is fixed, check whether the domains can be resolved properly. If yes, wait 3 minutes and then go to the CVM console to confirm whether there is monitoring data.

    Step 3. Check whether the UUID is correct

    Currently, the incorrect UUID configuration issue occurs only in Linux OS. For details, see the following directions.

    1. Log in to the CVM console and go to the instance detail page to view the UUID.
    2. Log in to the CVM instance and run the following command to view the UUID:
      cat /sys/class/dmi/id/product_serial
      
      If the UUID on the server is different from that displayed in the CVM console, run the following command as the root account to fix the UUID and restart the agents:
      echo `cat /etc/uuid |awk -F '= ' '{print $NF}'` > /etc/uuid_to_serial; mount --bind /etc/uuid_to_serial /sys/class/dmi/id/product_serial
      cd /usr/local/qcloud/stargate/admin
      ./restart.sh
      cd /usr/local/qcloud/monitor/barad/admin
      ./stop.sh
      ./trystart.sh
      
    Note:

    After fixing the UUID, wait 3 minutes and then go to the CVM console to confirm whether there is monitoring data.

    Step 4. Check the CVM instance log

    After the CVM instance is shut down, the instance's agents will be taken offline and thus no data will be reported.
    When you perform CVM Ops operations such as restart, upgrade, reinstallation, or image creation through the CVM console or through logging in to the CVM instance, the reporting of the CVM monitoring data may time out and the agents will be taken offline.

    Troubleshooting: You can access the detail page of the CVM instance and view the operation logs to determine whether any relevant Ops operations were performed on the CVM instance at that time.

    Step 5. Check the CVM instance load

    The agents may fail to report data if the CPU usage, memory usage, or bandwidth utilization of the CVM instance is too high.

    Troubleshooting methods:

    • High CPU usage: For detailed troubleshooting directions, see CVM CPU/Memory Usage Is Too High.
    • High memory usage: You can log in to the CVM instance or view the monitoring charts to check whether the CPU usage reaches 100%. If yes, upgrade the CVM configuration as needed.
    • High bandwidth utilization: For detailed troubleshooting directions, see CVM Bandwidth Utilization Is Too High.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support