What Should I Do If the Monitoring Is Periodically Interrupted or the Agent Status Keeps Changing?

Symptom

Monitoring interruptions and unstable Agent status may be caused by Agent overload. The Agent is overloaded if you see either of the following symptoms:

• On the Server Monitoring page, the Agent status frequently changes between Running and Faulty.
• The period in the metric dashboard is discontinuous.

Constraints

The restoration method in this section only supports new Agent version. If your Agent is of an earlier version, you are advised to upgrade it to the new version.

• Linux:
  1. Log in to the server as user root.
  2. Check the Agent version:

     if [[ -f /usr/local/uniagent/extension/install/telescope/bin/telescope ]]; then
     /usr/local/uniagent/extension/install/telescope/bin/telescope -v; elif [[ -f /usr/local/telescope/bin/telescope ]]; then echo "old agent"; else echo 0; fi

     • If old agent is returned, the earlier version of the Agent is used. Manage the Agent based on its version.
     • If a version is returned, the new version of the Agent is in use. Manage the Agent based on its version.
     • If 0 is returned, the Agent is not installed.
• Windows: Determine the Agent version based on the installation path. Default installation paths:
  • New version: C:\Program Files\uniagent\extension\install\telescope
  • Earlier version: C:\Program Files\telescope

Possible Causes

The circuit patter is implemented by the Agent when the CPU and memory usage is too high to prevent other services from being affected. The circuit breaker pattern will be implemented automatically when the Agent is overloaded, and no monitoring data will not be reported.

Circuit Breaker Principles

By default, the Agent detection system is as follows:

The system checks the CPU usage and memory usage of the Agent process every minute. If the CPU usage exceeds 30% or the memory usage exceeds 700 MB, that is, the second threshold, the Agent process will exit. If both the CPU usage and memory usage do not exceed the second threshold, the system checks whether they exceed the first threshold (10% of CPU usage or 200 MB of memory usage). If any of them exceeds the first threshold for three consecutive times, the Agent process will exit and the information will be recorded.

Procedure

1. Log in to the ECS or BMS where the Agent does not report data.
2. Optional: Go to the Agent installation path.

   For Windows, the path is C:\Program Files\uniagent\extension\install\telescope\bin.

   For Linux, the path is /usr/local/uniagent/extension/install/telescope/bin.

3. Modify configuration file conf.json.
   1. Run the following command to open conf.json:

      vi conf.json

   2. Add the following parameters to the conf.json file. For details about the parameters, see Table 1.

      Table 1 Parameters

      Parameter	Description
      cpu_first_pct_threshold	Tier-1 threshold of CPU usage. The default value is 10 (%).
      memory_first_threshold	Tier-1 threshold of memory usage. The default value is 209715200 (200 MB). The unit is byte.
      cpu_second_pct_threshold	Tier-2 threshold of CPU usage. The default value is 30 (%).
      memory_second_threshold	Tier-2 threshold of memory usage. The default value is 734003200 (700 MB). The unit is byte.
      To query the CPU usage and memory usage of the Agent process, use either of the following methods: Linux: top -p telescope PID Windows: View the details about the Agent process in Task Manager.

      {
          "cpu_first_pct_threshold": xx,
          "memory_first_threshold": xxx,
          "cpu_second_pct_threshold": xx,
          "memory_second_threshold": xxx
      }

   3. Save the conf.json file and exit.

      :wq

4. Restart the Agent.
   • Windows:
     1. In the C:\Program Files\uniagent\extension\install\telescope directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
     2. In the C:\Program Files\uniagent\script directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
   • Linux:

     service ces-uniagent stop
     service ces-uniagent start
     /usr/local/uniagent/extension/install/telescope/telescoped restart