Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Cloud Eye/ FAQs/ Server Monitoring/ Agent Installation/ What Should I Do If the Monitoring Is Periodically Interrupted or the Agent Status Keeps Changing?

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

Updated on 2024-01-11 GMT+08:00

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 of the Cloud Eye console, 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.

Run the following command to check the current 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 displayed, the Agent version is old.
  • If a version ID is returned, the Agent version is new.
  • If 0 is returned, the Agent has not been installed.

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 mechanism is as follows:

The Agent resource usage will be checked every one minute. If the resource usage exceeds the tier-2 thresholds (30% of CPU usage and 700 MB memory usage), the Agent exists. If the tier-1 thresholds (10% CPU usage and 200 MB memory usage) for three consecutive times, the Agent also exists and a record will be generated.

After the Agent exits, the daemon process automatically starts the Agent process and checks the exit records. If there are three consecutive exit records, the Agent will hibernate for 20 minutes, during which monitoring data will not be collected.

When too many disks are attached to a server, the CPU or memory usage of the Agent process will become high. You can configure the tier-1 and tier-2 thresholds based on Procedure to trigger the circuit-breaker pattern according to the actual resource usages.

Procedure

  1. Use the root account to log in to the ECS or BMS for which 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.

    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.

      a To query the CPU usage and memory usage of the Agent, use the following method:

      • 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. Run the following command to save and exit the conf.json file:

      :wq

  4. Restart the Agent:
    • Windows:
      • In the directory where the Agent installation package is stored, double-click the shutdown.bat script to stop the Agent, and then execute the start.bat script to start the Agent.
    • Linux:
      • Run the following command to check the PID of telescope:
      • ps -ef |grep telescope
      • After the process is forcibly stopped, wait for 3 to 5 minutes for the Agent to automatically restart. Figure 1 shows an operation example.
      • kill -9 PID
        Figure 1 Restarting the Agent

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback