- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Overview
- Permissions Management
-
Cloud Resource Monitoring
- Resource Groups
-
Server Monitoring
- Overview
- Cloud Eye Plug-in (Agent)
- Process Monitoring
- Viewing Server Monitoring Metrics
- Creating an Alarm Rule to Monitor a Server
- Viewing Server Monitoring Details
- Cloud Service Monitoring
- Task Center
- Visualization (Dashboards)
-
Alarm Management
- Overview
- Alarm Rules
- Alarm Records
-
Alarm Templates
- Viewing Alarm Templates
- Creating a Custom Template or Custom Event Template
- Modifying a Custom Template or Custom Event Template
- Deleting a Custom Template or Custom Event Template
- Copying a Custom Template or Custom Event Template
- Associating a Custom Template with a Resource Group
- Importing and Exporting Custom Template or Custom Event Templates
- Alarm Notifications
- Example: Creating an Alarm Rule to Monitor ECS CPU Usage
- One-Click Monitoring
- Alarm Masking
- Event Monitoring
- Access Center
- Data Dump
- Quotas and Audit
- Cloud Product Metrics
- Change History
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API V1
- API Version Management
- Metrics
-
Alarm Rules
- Querying Alarm Rules
- Querying Details of an Alarm Rule
- Enabling or Disabling an Alarm Rule
- Deleting an Alarm Rule
- Creating an Alarm Rule
- Creating a Custom Alarm Template
- Deleting a Custom Alarm Template
- Querying the Alarm History of an Alarm Rule
- Querying Custom Alarm Templates
- Updating a Custom Alarm Template
- Modifying an Alarm Rule
- Monitoring Data
- Quotas
- Resource Groups
- Event Monitoring
-
API V2
- Alarm Rules
- Resources in an Alarm Rule
- Alarm Policies
- Alarm Notifications
- Alarm Records
- Alarm Templates
- Alarm Rules Associated with an Alarm Template
- Resource Groups
- Resources in a Resource Group
-
One-Click Monitoring
- Enabling One-Click Monitoring
- Querying Services and Resources That Support One-Click Monitoring
- Querying Alarm Rules of One Service in One-Click Monitoring
- Batch Enabling or Disabling Alarm Rules of One Service in One-Click Monitoring
- Batch Disabling One-Click Motoring
- Batch Modifying Alarm Notifications in Alarm Rules for One Service That Has One-Click Monitoring Enabled
- Batch Enabling or Disabling Alarm Policies in Alarm Rules for One Service That Has One-Click Monitoring Enabled
-
Alarm Notification Masking
- Creating Alarm Notification Masking Rules in Batches
- Modifying the Masking Time of Alarm Notification Masking Rules in Batches
- Modifying an Alarm Notification Masking Rule
- Deleting Alarm Notification Masking Rules in Batches
- Querying Alarm Notification Masking Rules
- Querying Resources for Which Alarm Notifications Have Been Masked
- Dashboards
- Graphs
- Resource Tags
- Metric Management
- API V3
-
Permissions Policies and Supported Actions
- Introduction
- Supported Actions of the API Version Management APIs
- Supported Actions of the Metric Management API
- Supported Actions of the Alarm Rule Management APIs
- Supported Actions of the Monitoring Data Management APIs
- Supported Actions of the Quota Management API
- Supported Actions of the Event Monitoring API
- Common Parameters
- Appendix
- Change History
- SDK Reference
-
FAQs
-
General Consulting
- What Is Rollup?
- How Long Is Metric Data Retained?
- How Many Rollup Methods Does Cloud Eye Support?
- How Can I Export Collected Data?
- What Should I Do If I See Garbled Chinese Characters in an Exported CSV File?
- Why Can't a User of an Enterprise Project View the One-Click Monitoring Function?
- Why Can't a User of an Enterprise Project Select All Resources When Configuring Alarm Rules?
-
Server Monitoring
-
Agent Installation
- How Do I Configure DNS and Security Groups?
- How Do I Configure an Agency?
- How Does the Cloud Eye Agent Obtain a Temporary AK/SK by Authorization?
- What OSs Does the Agent Support?
- Resource Usage and Circuit Breaker Pattern of Agent
- What Should I Do If the Monitoring Is Periodically Interrupted or the Agent Status Keeps Changing?
- What Should I Do If a Service Port Is Used by the Agent?
- Troubleshooting Agent One-Click Restoration Failures
- No Monitoring Data Is Displayed After One-Click Restoration Performed for the Agent
- Does the Server Monitoring Agent Affect Server Performance?
- Troubleshooting the Problem of Reported Metrics Being Discarded
- Metrics
-
Agent Statuses
- How Can I Quickly Restore Agent Configurations?
- What Should I Do If the Agent Status Is Faulty?
- What Should I Do If the Agent Status Is Stopped?
- What Should I Do If the Agent Status Is Running But There Is No Monitoring Data?
- What Can I Do If No Monitoring Data Is Displayed After One-Click Agent Restoration? (Old Agent)
- How Can I Enable the OS Monitoring for a New ECS?
- Agent Status Description and Troubleshooting Methods
- How Do I Obtain Debug Logs of the Agent?
-
Agent Installation
-
Alarm Notifications or False Alarms
- What Is an Alarm Notification? How Many Types of Alarm Notifications Are There? How Can I Configure an Alarm Notification?
- What Alarm Status Does Cloud Eye Support?
- What Alarm Severities Does Cloud Eye Support?
- When Will an "Insufficient data" Alarm Be Triggered?
- How Do I Monitor and View the Disk Usage?
- How Can I Change the Phone Number and Email Address for Receiving Alarm Notifications?
- How Can a User Account Receive Alarm Notifications?
- Why Did I Receive a Bandwidth Overflow Notification While There Being No Bandwidth Overflow Record in the Monitoring Data?
-
Monitored Data Exceptions
- Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
- Why I Cannot See the Monitoring Data on the Cloud Eye Console After Purchasing Cloud Service Resources?
- Why Doesn't the Cloud Eye Console Display the OS Monitoring Data or Why Isn't the Data Displayed Immediately After the Agent Is Installed and Configured on an ECS?
- Why Is Basic Monitoring Data Inconsistent with Data Monitored by the OS?
- Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?
- Why Is the Metric Collection Point Lost During Certain Periods of Time?
- Why Are the Four Metrics Memory Usage, Disk Usage, Inband Incoming Rate, and Inband Outgoing Rate Not Displayed for an ECS?
- What Are the Impacts on ECS Metrics If UVP VMTools Is Not Installed on ECSs?
- Why Are the Inbound Bandwidth and Outbound Bandwidth Negative?
- Metric Descriptions
-
User Permissions
- What Should I Do If the IAM Account Permissions Are Abnormal?
- What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Access Cloud Eye?
- What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?
-
General Consulting
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Product Introduction
- Getting Started
- Dashboards
- Resource Groups
- Using the Alarm Function
-
Server Monitoring
- Introduction to Server Monitoring
- Agent Installation and Configuration
- Agent Features per Version
- Installing and Configuring the Agent on a Linux ECS or BMS
- Installing and Configuring the Agent on a Windows ECS
- Installing the Agents in Batches on Linux ECSs
- Managing the Agent
- Installing the Direct Connect Metric Collection Plug-ins
- Process Monitoring
- Viewing Server Monitoring Metrics
- Creating an Alarm Rule to Monitor a Server
- Custom Monitoring
- Event Monitoring
- Task Center
- Data Dump
- Cloud Service Monitoring
- Auditing Operation Records on Cloud Eye
- Permissions Management
- Quota Adjustment
- Services Interconnected with Cloud Eye
-
FAQs
-
General Consulting
- What Is Rollup?
- How Long Is Metric Data Retained?
- How Many Rollup Methods Does Cloud Eye Support?
- How Can I Export Collected Data?
- Which Services Does Cloud Eye Support Permission- and Region-based Monitoring in the Enterprise Project Dimension?
- Which Cloud Eye Resources Support the Enterprise Project Feature?
- Why Can a User of an Enterprise Project View the Resource Information of the Account on the Overview Page?
-
Server Monitoring
- How Can I Quickly Restore the Agent Configuration?
- How Can I Make a Newly Purchased ECS Monitor Its OS?
- Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?
- What OSs Does the Agent Support?
- What Statuses Does the Agent Have?
- What Should I Do If the Monitoring Period Is Interrupted or the Agent Status Keeps Changing?
- What Should I Do If the Service Port Is Used by the Agent?
- How Can I Create an Agency?
- What Can't I Create Another Agency?
- What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?
- What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?
- Will the Agent Affect the Server Performance?
- What Should I Do If the Agent Status Is Faulty?
- What Should I Do If the Agent Status Is Stopped?
- What Should I Do If the Agent Status Is Running But There Is No Monitoring Data?
- How Do I Troubleshoot the Agent One-Click Restoration Failure?
- What Can I Do If No Monitoring Data Is Displayed After One-Click Agent Restoration?
-
Alarm Notifications or False Alarms
- What Is an Alarm Notification? How Many Types of Alarm Notifications Are There?
- What Alarm Status Does Cloud Eye Support?
- What Alarm Severities Does Cloud Eye Support?
- When Will an "Insufficient data" Alarm Be Triggered?
- How Do I Monitor and View the Disk Usage?
- How Can I Change the Mobile Number and Email Address for Receiving Alarm Notifications?
- How Can an IAM User Receive Alarm Notifications?
- Why Did I Receive a Bandwidth Overflow Notification While There Being No Bandwidth Overflow Record in the Monitoring Data?
-
Monitored Data Exceptions
- Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
- Why I Cannot See the Monitoring Data on the Cloud Eye Console After Purchasing Cloud Service Resources?
- Why Is OS Monitoring Data Not Displayed or Not Displayed Immediately After the Agent Is Installed and Configured on a server?
- Why Is Basic Monitoring Data Inconsistent with the Data Monitored by the OS?
- Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?
- Why Is the Metric Collection Point Lost During a Certain Period of Time?
- Why Are Memory Usage, Disk Usage, Inband Incoming Rate, and Inband Outgoing Rate Not Displayed for an ECS?
- What Are the Impacts on ECS Metrics If UVP VMTools Is Not Installed on ECSs?
- Why Are the Inbound Bandwidth and Outbound Bandwidth Negative?
- Metric Descriptions
- User Permissions
-
General Consulting
-
API Reference (ME-Abu Dhabi Region)
- Before You Start
- API Overview
- Calling APIs
- API DescriptionAPI V1
- API v2
-
Permissions Policies and Supported Actions
- Introduction
- Supported Actions of the API Version Management APIs
- Supported Actions of the Metric Management API
- Supported Actions of the Alarm Rule Management APIs
- Supported Actions of the Monitoring Data Management APIs
- Supported Actions of the Quota Management API
- Supported Actions of the Event Monitoring API
- Common Parameters
- Appendix
- Change History
-
User Guide (Paris Region)
- Product Introduction
- Getting Started
- Monitoring Panels
- Using the Alarm Function
- Custom Monitoring
- Services Interconnected with Cloud Eye
- FAQs
- Change History
- API Reference (Paris Region)
-
User Guide (Kuala Lumpur Region)
- Product Introduction
- Getting Started
- Dashboards
- Resource Groups
- Using the Alarm Function
-
Server Monitoring
- Introduction to Server Monitoring
- Agent Installation and Configuration
- Agent Features per Version
- Installing and Configuring the Agent on a Linux ECS or BMS
- Installing and Configuring the Agent on a Windows ECS
- Installing the Agents in Batches on Linux ECSs
- Managing the Agent
- Process Monitoring
- Viewing Server Monitoring Metrics
- Creating an Alarm Rule to Monitor a Server
- Custom Monitoring
- Event Monitoring
- Data Dump
- Auditing Operation Records on Cloud Eye
- Permissions Management
- Quota Adjustment
- Services Interconnected with Cloud Eye
-
FAQs
- General Consulting
-
Server Monitoring
- How Can I Quickly Restore the Agent Configuration?
- Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?
- What OSs Does the Agent Support?
- What Statuses Does the Agent Have?
- What Should I Do If the Monitoring Period Is Interrupted or the Agent Status Keeps Changing?
- What Should I Do If the Service Port Is Used by the Agent?
- How Can I Create an Agency?
- What Can't I Create Another Agency?
- What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?
- What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?
- Will the Agent Affect the Server Performance?
- What Should I Do If the Agent Status Is Faulty?
-
Alarm Notifications or False Alarms
- What Is an Alarm Notification? How Many Types of Alarm Notifications Are There?
- What Alarm Status Does Cloud Eye Support?
- What Alarm Severities Does Cloud Eye Support?
- When Will an "Insufficient data" Alarm Be Triggered?
- How Can I Change the Mobile Number and Email Address for Receiving Alarm Notifications?
- How Can an IAM User Receive Alarm Notifications?
- Why Did I Receive a Bandwidth Overflow Notification While There Being No Bandwidth Overflow Record in the Monitoring Data?
-
Monitored Data Exceptions
- Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
- Why I Cannot See the Monitoring Data on the Cloud Eye Console After Purchasing Cloud Service Resources?
- Why Is OS Monitoring Data Not Displayed or Not Displayed Immediately After the Agent Is Installed and Configured on a server?
- Why Is Basic Monitoring Data Inconsistent with the Data Monitored by the OS?
- Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?
- Why Is the Metric Collection Point Lost During a Certain Period of Time?
- Why Are Memory Usage, Disk Usage, Inband Incoming Rate, and Inband Outgoing Rate Not Displayed for an ECS?
- What Are the Impacts on ECS Metrics If UVP VMTools Is Not Installed on ECSs?
- User Permissions
- Change History
- API Reference (Kuala Lumpur Region)
-
User Guide (Ankara Region)
- Product Introduction
- Getting Started
- Dashboards
- Resource Groups
- Using the Alarm Function
-
Server Monitoring
- Introduction to Server Monitoring
- Agent Installation and Configuration
- Installing and Configuring the Agent on a Linux ECS
- Installing and Configuring the Agent on a Windows ECS
- Installing the Agents in Batches on Linux ECSs
- Managing the Agent
- Process Monitoring
- Viewing Server Monitoring Metrics
- Creating an Alarm Rule to Monitor a Server
- Custom Monitoring
- Event Monitoring
- Cloud Service Monitoring
- Permissions Management
- Quota Adjustment
- Services Interconnected with Cloud Eye
-
FAQs
- General Consulting
-
Server Monitoring
- How Can I Quickly Restore the Agent Configuration?
- What OSs Does the Agent Support?
- How Do I Query the Current Agent Version?
- What Should I Do If the Service Port Is Used by the Agent?
- How Can I Create an Agency?
- What Can't I Create Another Agency?
- What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?
- What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?
- Will the Agent Affect the Server Performance?
- What Should I Do If the Agent Status Is Faulty?
- Alarm Notifications or False Alarms
- Monitored Data Exceptions
- User Permissions
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
(Optional) Manually Configuring the Agent (Linux)
After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.
Prerequisites
You have installed the Agent.
Checking the Version of the Agent In Use
- Log in to an ECS as user root.
- Run the following command to 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 early version of the Agent is used. For details about how to manually configure the Agent, see Procedure (Agent of the Earlier Version).
- If a version is returned, the new version of the Agent is used. For details about how to manually configure the Agent, see Procedure (for the New Version of the Agent).
- If 0 is returned, the Agent is not installed.
Procedure (for the New Version of the Agent)
- Log in to an ECS as user root.
- Modify the conf.json file in the bin directory.
- Open conf.json:
vi /usr/local/uniagent/extension/install/telescope/bin/conf.json
- Modify the parameters in the file. For details, see Table 1.
NOTICE:
Storing plaintext AKs and SKs poses great security risks. You are advised to delegate all ECS or BMS Agents in the region. For details, see How Do I Configure an Agency?
{ "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "AccessKey": "XXXXXXXXXXXXXXXXXXXX", "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "RegionId": "ap-southeast-1", "ClientPort": 0, "PortNum": 200 }
Table 1 Public parameters Parameter
Description
InstanceId
(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list.
NOTE:
If you do not configure InstanceId, retain "InstanceId":"". If you configure it, ensure that the following two requirements are met:
- The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur.
- The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
ProjectId
(Optional) Specifies the project ID. If you do not configure ProjectId, retain "ProjectId": "".
If you configure it, perform the following operations:
- Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
- Under Projects, obtain the project ID for the region where the ECS or BMS is located.
AccessKey/SecretKey
To obtain the AK and SK, perform the following operations:
Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys.
- If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys.
- If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it.
NOTICE:
- For the security purpose, use an IAM username with the CES Administrator and LTS Administrator permissions.
- The configured access key must be within the Access Keys list on the My Credentials page. Otherwise its authentication will fail and you cannot view OS monitoring data on Cloud Eye.
RegionId
Specifies the region ID. For example, if the ECS or BMS is located in the CN-Hong Kong region, RegionId is ap-southeast-1. For IDs of other regions, see https://developer.huaweicloud.com/intl/en-us/endpoint.
ClientPort
Specifies the start port number used by the Agent.
NOTE:
The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
PortNum
Specifies the number of ports configured for the Agent.
NOTE:
The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.
BmsFlag
Set this parameter to true for a BMS. This parameter is not required by an ECS.
You do not need to set this parameter for the Windows OS.
- Open conf.json:
Procedure (Agent of the Earlier Version)
- Log in to an ECS as user root.
- Go to the Agent installation path bin:
cd /usr/local/uniagent/extension/install/telescope/bin
- Modify configuration file conf.json.
- Open conf.json:
vi conf.json
- Modify the parameters in the file. For details, see Table 2.
ECS parameters
{ "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "AccessKey": "XXXXXXXXXXXXXXXXXXXX", "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "RegionId": "ap-southeast-1", "ClientPort": 0, "PortNum": 200 }
BMS parameters
{ "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "AccessKey": "XXXXXXXXXXXXXXXXXXXX", "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "RegionId": "ap-southeast-1", "ClientPort": 0, "PortNum": 200, "BmsFlag": true }
Table 2 Public parameters Parameter
Description
InstanceId
(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list.
NOTE:
If you do not configure InstanceId, retain "InstanceId":"". If you configure it, ensure that the following two requirements are met:
- The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur.
- The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
ProjectId
(Optional) Specifies the project ID. If you do not configure ProjectId, retain "ProjectId": "".
If you configure it, perform the following operations:
- Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
- Under Projects, obtain the project ID for the region where the ECS or BMS is located.
AccessKey/SecretKey
To obtain the AK and SK, perform the following operations:
Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys.
- If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys.
- If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it.
NOTICE:
- For the security purpose, use an IAM username with the CES Administrator and LTS Administrator permissions..
- The configured access key must be within the Access Keys list on the My Credentials page. Otherwise its authentication will fail and you cannot view OS monitoring data on Cloud Eye.
RegionId
Specifies the region ID. For example, if the ECS or BMS is located in the CN-Hong Kong region, RegionId is ap-southeast-1. For IDs of other regions, see https://developer.huaweicloud.com/intl/en-us/endpoint.
ClientPort
Specifies the start port number used by the Agent.
NOTE:
The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
PortNum
Specifies the number of ports configured for the Agent.
NOTE:
The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.
BmsFlag
Set this parameter to true for a BMS. This parameter is not required by an ECS.
You do not need to set this parameter for the Windows OS.
- Open conf.json:
- Modify configuration file conf_ces.json for the Cloud Eye metric collection module.
- Run the following command to open public configuration file conf_ces.json:
vi conf_ces.json
- Modify the endpoint in conf_ces.json, and save the conf_ces.json file. For details, see Table 3.
{ "Endpoint": "https://ces.ap-southeast-1.myhuaweicloud.com" }
Table 3 Parameter setting of the metric collection module Parameter
Description
Endpoint
Specifies the Cloud Eye endpoint URL in the region where the ECS or BMS is located. For example, if the ECS or BMS is in the CN-Hong Kong region, Endpoint is ces.ap-southeast-1.myhwclouds.com. For the endpoint values of other regions, see https://developer.huaweicloud.com/intl/en-us/endpoint.
NOTE:
- After you configure the Agent, its status is still displayed as Uninstalled because the monitoring data is not reported yet. Wait 3 to 5 minutes and refresh the page.
- If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
- Run the following command to open public configuration file conf_ces.json:
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot