CloudLens for Elastic Block Storage (EBS) reports risk events when the disk performance data reaches a specific upper limit or snapshots are not created for data backup. This helps you handle the events at the earliest opportunity to ensure stable disk operation and data security. This topic describes the types of risk events that can be reported by CloudLens for EBS, descriptions of events, and suggestions on how to handle different events.
Event attributes
Event attribute | Description |
EventName | The name of the event. |
ResourceId | The ID of the disk associated with the event. |
ResourceType | The type of the resource associated with the event. Example: disk. |
Description | The description of the event. |
EventType | The type of the event. Valid values:
|
EventLevel | The level of the event. Valid values:
|
EventId | The ID of the event. The ID of each event is unique on the instance. |
EventStatus | The status of the event. Valid values:
|
StartTime | The start time of the event. |
EndTime | The end time of the event. |
RecommendAction | The action recommended for the event. Valid values:
|
RecommendParam | Parameter used in processing the event. For example, this parameter is set to a recommended provisioned value when the system processes a Cost Optimization event. |
To query the attributes of a specific event, go to the Risk Event page in the EBS console or call the DescribeEvents operation.
Event handling suggestions
The following table describes the suggestions on how to handle different events.
Event name | Description | Report frequency | Event type | Event level | Suggestion | Whether the event status is recovered |
Data Protection | You did not create snapshots for a disk for an extended period of time. In this case, you may be unable to restore the disk to the most recent state in the event of ransomware, which may cause data loss. | Every morning | Alert | Warn | After the disk is restored, the system pushes a new event in the Recovered state for the disk the next morning. The Active event that was pushed remains. | |
Cost Optimization |
You can change the provisioned values to balance performance and cost. For more information, see ESSD AutoPL disks. | Once a week | Alert | Info | After the disk is restored, no events of the same type are pushed. | |
Disk I/O Hang | An I/O hang occurred when the operating system became unstable or experienced downtime due to the excessively high read/write I/O latency of file systems on a disk. | Real time | SystemException | Critical | View the performance metrics of disks to identify the cause. For more information, see View the monitoring data of a disk. For information about how an Alibaba Cloud Linux operating system detects I/O hangs, see Detect I/O hangs of file systems and block layers. | After the disk is restored, the system pushes a new event in the Recovered state for the disk. The Active events that were pushed remains. |
Specification Mismatch Between the Instance and Disks | The total specifications of disks on an instance exceed the upper limit supported by the instance type. The maximum disk performance may be limited by the instance type. For example, if an ECS instance has a maximum IOPS of 60,000 and a disk that has a maximum IOPS of 100,000 is attached to the instance, the performance of the disk is limited by the instance type.
| From 12: 00 to 15: 00 every day | Alert | Warn | When the total performance of disks on an instance exceeds the performance upper limit supported by the instance type, issues such as slow data processing and long response latency may occur. We recommend that you change the instance type based on your business requirements. For more information, see Upgrade the instance types of subscription instances and Change the instance type of a pay-as-you-go instance. | After the disk is restored, no events of the same type are pushed for the disk. |
Total IOPS of Disks Reached Maximum IOPS per Instance | The total number of IOPS of disks attached to an instance reached the upper limit for the instance. For example, the maximum IOPS of an ECS instance is 60,000 and two disks are attached to the instance. The IOPS of a disk is 10,000 and the IOPS of the other disk is 51,000. The total real-time IOPS of the disks on the instance reaches the maximum IOPS of the instance.
| Within 5 minutes after the event is triggered Note The time is accurate to 5 minutes, and latency is measured in minutes. | Notification | Warn | When the event is triggered, another event in the Recovered state is reported to remind you that the issue occurs on the current disks, regardless of whether the Active event is handled. | |
Total BPS of Disks Reached Maximum BPS per Instance | The total bytes per second (BPS) of disks on your instance reached the upper limit for the instance. For example, the maximum BPS of an ECS instance is 150 MB/s, and two disks are attached to the instance. The BPS of a disk is 100 MB/s, and the BPS of the other disk is 60 MB/s. In this case, the total real-time BPS (160 MB/s) of the disks exceeds the maximum BPS for the instance.
| Notification | Warn | |||
IOPS of a Disk Reached Maximum IOPS per Instance | The IOPS of your disk reached the upper limit for the instance. For example, an ECS instance has a maximum IOPS of 60,000, several disks are attached to the instance, and one disk has the IOPS of 70,000. In this case, the real-time IOPS of the disks exceeds the maximum IOPS for the instance.
| Notification | Warn | |||
BPS of a Disk Reached Maximum BPS per Instance | The BPS of your disk reached the upper limit for the instance. For example, the maximum BPS of an ECS instance is 150 MB/s, several disks are attached to the instance, and the BPS of one disk is 160 MB/s. In this case, the real-time BPS of the disks exceeds the upper limit of the BPS for the instance.
| Notification | Warn | |||
IOPS of a Disk Reached Maximum IOPS per Disk | The IOPS of your disk reached the upper limit for the disk. For example, the IOPS of a PL0 Enterprise SSD (ESSD) attached to an ECS instance reaches 15,000 and the maximum IOPS of the disk is 10,000. In this case, the real-time IOPS of the PL0 ESSD exceeds the maximum IOPS of the disk.
| Notification | Warn | Issues such as slow data processing and high response latency may occur on the disk. For information about the performance metrics of different disk categories, see Block storage performance.
| ||
BPS of a Disk Reached Maximum BPS per Disk | The BPS of your disk reached the upper limit for the disk. For example, the BPS of a PL0 ESSD attached to an ECS instance reaches 200 MB/s, and the maximum BPS of the disk is 180 MB/s. In this case, the real-time BPS of the disk exceeds the maximum BPS of the disk.
| Notification | Warn | |||
Non-4K-Aligned Read/Write Operation | Read/write operations on your disk are not 4K-aligned, which may affect disk I/O performance. Note If read/write operations in partitions on the disk are not 4K-aligned, the disk may perform a read-modify-write operation across two 4K sectors. As a result, a read/write operation may involve multiple I/O operations, which degrades the performance of the disk. | From 12: 00 to 15: 00 every day | Notification | Info | For information about how to resolve the preceding issue, see the Improve IO performance with 4K alignment section of the "Query and Case Analysis Linux IO Load" topic. | |
Disk I/O Burst | Disk I/O Burst occurred on your disk, which may incur performance burst fees. For more information, see ESSD AutoPL disks. | Every 1 hour | Notification | Info | Check whether burst I/O of the disk meets your business expectations. |