Help Center > > Service Overview> What Is Cloud Eye?

What Is Cloud Eye?

Updated at: Feb 13, 2020 GMT+08:00

Cloud Eye is a multi-dimensional resource monitoring platform. You can use Cloud Eye to monitor the utilization of service resources, track the running status of cloud services, configure alarm rules and notifications, and quickly respond to resource changes. Figure 1 shows the Cloud Eye architecture.

Figure 1 Cloud Eye architecture

Cloud Eye provides the following functions:

  • Automatic Monitoring: Monitoring starts automatically after you create Elastic Cloud Servers (ECSs) or Auto Scaling (AS) groups. After deploying a cloud service, you can view the service running status and set alarm rules on the Cloud Eye console.
  • Server Monitoring: After installing the Agent (Telescope) on an ECS or BMS, you can collect 60-second granularity ECS or BMS monitoring data in real-time. 40 metrics, such as CPU, memory, and disk metrics, are provided. For details, see Introduction to Server Monitoring.
  • Flexible Alarm Rule Configuration: You can create alarm rules for multiple resources at the same time. After an alarm rule is created, you can flexibly manage it, for example at any time you can modify, enable, disable, or delete it.
  • Real-time Notification: You can enable Simple Message Notification (SMN) when creating alarm rules. When the cloud service status changes and the monitoring data of the metric reaches the threshold specified in an alarm rule, Cloud Eye notifies you by emails, or by sending messages to server addresses. In this way, you can monitor the cloud resource status and changes in real time.
  • Monitoring Panel: The panel enables you to view cross-service and cross-dimension monitoring data. It displays key metrics centrally, providing an overview of the service operating status and allowing monitoring details to be checked when troubleshooting.
  • Resource Groups: This function enables management of resources based on services, including management of ECSs, EVS disks, elastic IP addresses, bandwidth, and databases. Resources of different types, alarm rules, and alarm history are managed based on service, which helps to improve O&M efficiency.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel