Overview
Monitoring is important to ensure FlexusL instance performance, reliability, and availability. You can use Cloud Eye to monitor FlexusL instances and know their statuses. Cloud Eye can monitor a range of metrics, such as the CPU usage, disk usage, and bandwidth of FlexusL instances.
How Do I Use Monitoring?
After you purchase a FlexusL instance, Cloud Eye is enabled by default. It can monitor the cloud servers, EVS disks, and CBR vaults packaged in the FlexusL instances.
Cloud Server Monitoring
Server monitoring collects monitoring metrics at the OS layer of servers.
Server monitoring consists of basic monitoring, OS monitoring, and process monitoring. Basic monitoring does not require the Agent to be installed. OS monitoring and process monitoring require the Agent to be installed on the FlexusL instances to be monitored.
- Basic monitoring covers metrics automatically reported by FlexusL instances. The data is collected every 5 minutes. For details, see Table 1.
- OS monitoring provides proactive, fine-grained OS monitoring for FlexusL instances, and it requires the Agent to be installed on the FlexusL instances to be monitored. The data is collected every minute. In addition to the CPU usage, metrics such as memory usage can also be monitored. For details, see OS Monitoring Metrics.
- Process monitoring monitors active processes on FlexusL instances, and it requires the Agent to be installed on the FlexusL instances to be monitored. By default, Cloud Eye collects the CPU usage, memory usage, and the number of opened files of active processes.
Basic Monitoring Metric |
Description |
---|---|
CPU Usage |
CPU usage of the physical server accommodating the monitored cloud server (ECS), which is not accurate as that obtained from the ECS that is being monitored Unit: percentage (%) Formula: CPU usage of a cloud server (ECS)/Number of CPU cores on the cloud server (ECS) |
Disk Read Bandwidth |
Number of bytes read from the monitored object per second Unit: Byte/s Formula: Total number of bytes read from an EVS disk/Monitoring interval |
Disk Write Bandwidth |
Number of bytes written to the monitored object per second Unit: Byte/s Formula: Total number of bytes written to an EVS disk/Monitoring interval |
Disk Read IOPS |
Number of read requests sent to the monitored object per second Unit: Request/s Formula: Total number of read requests sent to an EVS disk/Monitoring interval |
Disk Write IOPS |
Number of write requests sent to the monitored object per second Unit: Request/s Formula: Total number of write requests sent to an EVS disk/Monitoring interval |
Outband Incoming Rate |
Number of incoming bytes received by the monitored object per second at the virtualization layer Unit: Byte/s Formula: Total number of outband incoming bytes on a cloud server (ECS)/Monitoring interval |
Outband Outgoing Rate |
Number of outgoing bytes sent by the monitored object per second at the virtualization layer Unit: Byte/s Formula: Total number of outband incoming bytes on a cloud server (ECS)/Monitoring interval |
Network Connections |
Total number of TCP and UDP connections on a cloud server (ECS) Unit: Count |
Server Inbound Bandwidth |
Number of public and private byte received by the cloud server (ECS) per second Unit: Byte/s |
Server Outbound Bandwidth |
Number of public and private byte sent by the cloud server (ECS) per second Unit: Byte/s |
Server Inbound PPS |
Number of public and private packets received by the cloud server (ECS) per second Unit: Packet/s |
Server Outbound PPS |
Number of public and private packets sent by the cloud server (ECS) per second Unit: Packet/s |
New Connections |
Number of new connections (including TCP, UDP, and ICMP) created on the cloud server (ECS) Unit: connect/s |
EVS Monitoring
EVS monitoring collects metrics of EVS disks every 5 minutes on average. For details, see Viewing EVS Monitoring Data.
CBR Monitoring
CBR monitoring collects metrics of the used vault size and vault usage of CBR every 15 minutes.
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