- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- My 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 GPU Metrics Collection Plug-in (Linux)
- 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
- Permissions Management
- Quota Adjustment
- Services Interconnected with Cloud Eye
- 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
-
Server Monitoring
- How Does the Cloud Eye Agent Obtain a Temporary AK/SK by Authorization?
- How Can I Quickly Restore the Agent Configuration?
- How Can I Ensure that a Newly Purchased ECS Comes with the OS Monitoring Function?
- 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 Changes?
- What Should I Do If the Service Port Is Used by the Agent?
- 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? 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?
-
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?
- Videos
Show all
Function Overview
-
Monitoring Panels
-
You can use monitoring panels to view core metrics and compare the performance data of different services.
You must create a monitoring panel before adding graphs. You can create a maximum of 20 monitoring panels.
Supported regions: EU-Dublin
-
-
Resource Groups
-
A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources. Resources of different types, alarm rules, and alarm history are managed based on the service, facilitating O&M efficiency.
The Resource Groups function supports enterprise projects. If a resource group is associated with an enterprise project, only users who have the permission of the enterprise project can view and manage the resource group.
Available in all regions.
-
-
Server Monitoring
-
Server monitoring performs basic monitoring, OS monitoring, and process monitoring for servers. Whether you are using ECSs or BMSs, you can use server monitoring to track various OS metrics, monitor server resource usage, and query monitoring data when faults occur.
- Basic monitoring involves metrics automatically reported by ECS, such as CPU usage. The data is collected every 5 minutes.
- OS monitoring provides system-wide, active, and fine-grained monitoring for servers, and requires Agents to be installed on the servers that will be monitored. The data is collected every 1 minute. OS monitoring supports metrics such as CPU usage and memory usage (Linux). For details, see Services Interconnected with Cloud Eye.
- Process monitoring is used to monitor active processes on hosts. By default, the Agent collects CPU usage, memory usage, and the number of opened files of the active processes. For details, see Services Interconnected with Cloud Eye.
-
-
Event Monitoring
-
In event monitoring, you can query system events that are automatically reported to Cloud Eye and custom events reported to Cloud Eye through the API. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you. Events are key operations on cloud service resources that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources, such as delete ECS or reboot ECS. For details, see Events Supported by Event Monitoring.
Available in all regions.
-
-
Alarm Management
-
You can set alarm rules for key metrics of cloud services. When the conditions in the alarm rule are met, Cloud Eye sends emails, or text messages, to you, or sends HTTP/HTTPS requests to the servers. You can quickly respond to resource changes.
Cloud Eye invokes the SMN APIs to send notifications to users. This requires you to create a topic and add subscriptions to this topic on the SMN console. Then when you create alarm rules on Cloud Eye, you can enable the alarm notification function and select the created topic. When an exception occurs, Cloud Eye can send the alarm information to the subscriptions in real time.
The Alarm Rules function supports enterprise projects. If an alarm rule is associated with an enterprise project, only users who have the permission of the enterprise project can view and manage the alarm rule.
Available in all regions.
-
-
Permissions Management
-
If you need to perform fine-grained permission management on Cloud Eye, you can use IAM to:
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing Cloud Eye resources.
- Grant only the permissions required for users to perform a task.
- Entrust a HUAWEI CLOUD account or cloud service to perform efficient O&M on your Cloud Eye resources.
Available in all regions.
-
-
APIs
-
Cloud Eye is a multi-dimensional resource monitoring platform. You can use Cloud Eye to monitor the resource usage and cloud service status. You can also configure alarm rules for the system to notify you of alarms, if any, so that you can quickly respond to ensure service running.
You can call APIs to perform operations on metrics, alarm rules, and monitoring data, such as querying the metric list and the alarm rule list, creating alarm rules, and deleting alarm rules. For details about all supported operations, see API Overview.
If you plan to access Cloud Eye through an API, ensure that you are familiar with Cloud Eye concepts. For details, see What Is Cloud Eye?
Available in all regions.
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.