• Cloud Eye

  1. Help Center
  2. Cloud Eye
  3. User Guide
  4. Product Introduction
  5. Basic Concepts

Basic Concepts

The following concepts are central to your understanding and use of Cloud Eye:


Metrics are the core concept in Cloud Eye. A metric refers to a quantized value of a resource dimension on the cloud platform, such as the ECS CPU usage and memory usage. A metric is a time-dependent variable that generates a series of monitoring data over time. It helps you understand the metric changes over a specified period of time.


Rollup is the process in which Cloud Eye calculates the average, maximum, minimum, sum, or variance value based on sample raw data reported by each cloud service in specific periods. The calculation period is called rollup period. Currently, Cloud Eye supports the following rollup periods: 5 minutes, 20 minutes, 1 hour, 4 hours, and 24 hours.

Monitoring Panels

Monitoring panels allow you to view monitoring data of custom metrics of different services and dimensions. It displays metrics of key services in a centralized way, so that you can get an overview of the service running status and check monitoring details when troubleshooting.


Topics are specified event for message publishing or notification subscription in SMN. Topics provide you with one-to-many publish subscription and message notification functions. You can send messages to different types of endpoints with only one message request. With SMN, Cloud Eye uses various methods to notify you of cloud service resource changes, helping you track running status of cloud services in a timely manner.

Alarm Rules

In an alarm rule, you can set the threshold for a cloud service metric. When the status (such as Alarm and OK) of the alarm rule changes, Cloud Eye notifies you by sending emails, text messages, or by sending HTTP/HTTPS requests, avoiding service loss due to resource problems.

Alarm Templates

An alarm template contains one or more alarm rules for a specific service. It can help you quickly create alarm rules for multiple cloud services. This also improves the working efficiency of the O&M personnel.

User Permission

By default, the public cloud system provides two types of user permissions by default: user management and resource management. User management permissions can manage users, user groups, and user group permissions. Resource management permissions can control users' operations on cloud service resources.

For details about Cloud Eye user permissions, see Permissions.


Regions are divided from the dimensions of geographical location and network latency. Public services, such as Object Storage Service (OBS), Virtual Private Cloud (VPC), and Image Management Service (IMS), are shared within the same region. Users can select a region closest to them to reduce access latencies.

Availability Zone (AZ)

A physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through the internal network. To enhance application availability, you are advised to create instances in different AZs.


A project is used to group and isolate OpenStack resources, such as computing, storage, and network resources. A project can either be a department or a project team. Multiple projects can be created for a single account.