This topic summarizes the system events supported by Elastic Compute Service (ECS) and provides suggestions on how to handle these events.
Note If Undefined is displayed in the Event name column of a system event, the system event is not displayed in the ECS console and cannot be queried by calling API operations. Example: the Instance:StateChange event.
Scheduled O&M events
| Event description | Event name | Event severity | CloudMonitor event | Reason why and time when a system event is triggered | Handling suggestion |
|---|---|---|---|---|---|
| Scheduled instance restart due to system maintenance | SystemMaintenance.Reboot | Critical |
| This system event is triggered 24 to 48 hours before the scheduled time of system maintenance when Alibaba Cloud detects a potential risk of hardware or software failure in the underlying host of an instance. | We recommend that you take one of the following actions in response to the event:
Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Scheduled instance stop due to system maintenance | SystemMaintenance.Stop | Critical |
| This system event is triggered 24 to 48 hours before the scheduled time of system maintenance when Alibaba Cloud detects a potential risk of hardware or software failure in the underlying host of an instance. | We recommend that you take one of the following actions in response to the event:
Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Scheduled instance redeployment due to system maintenance | SystemMaintenance.Redeploy | Critical |
| This system event is triggered 24 to 48 hours before the scheduled time of system maintenance when Alibaba Cloud detects a potential risk of hardware or software failure in the underlying host of an instance. Note Only instances that depend on host hardware support this system event, such as instances that are equipped with local disks or support SGX encrypted computing. | We recommend that you make preparations such as modifying the /etc/fstab configuration file and backing up data, and then take one of the following actions in response to the event:
Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Isolation of damaged local disks due to system maintenance | SystemMaintenance.IsolateErrorDisk | Critical |
| This system event is immediately triggered when Alibaba Cloud detects a hardware or software damage in a local disk of an instance. Important The procedure to handle a damaged local disk of an instance varies based on the instance type. For specific instance types, the instance must be restarted and the damaged local disk must be isolated. For other instance types, the damaged local disk can be isolated online and repaired. | We recommend that you make preparations such as modifying the /etc/fstab configuration file and backing up data, and then select an appropriate point in time to authorize the damaged disk to be isolated. Then, the local disk is isolated online without the need to restart its associated instance. Note For more information, see the "Scenario ③" section in O&M scenarios and system events for instances equipped with local disks. |
| Re-initialization of damaged local disks due to system maintenance | SystemMaintenance.ReInitErrorDisk | Critical |
| This system event is immediately triggered when Alibaba Cloud isolates and replaces a local disk on the host of an instance after Alibaba Cloud detects a hardware or software damage in the local disk. In most cases, Alibaba Cloud isolates and replaces a damaged local disk within five business days after you authorize Alibaba Cloud to isolate the local disk. Important The procedure to handle a damaged local disk of an instance varies based on the instance type. For specific instance types, the instance must be restarted and the damaged local disk must be isolated. For other instance types, the damaged local disk can be isolated online and repaired. | We recommend that you select an appropriate point in time to authorize the local disk to be restored. Then, the local disk is restored online without the need to restart its associated instance. Note For more information, see the "Scenario ③" section in O&M scenarios and system events for instances equipped with local disks. |
| Isolation of damaged local disks and instance restart due to system maintenance | SystemMaintenance.RebootAndIsolateErrorDisk | Critical |
| This system event is immediately triggered when Alibaba Cloud detects a hardware or software damage in a local disk of an instance and fails to isolate the local disk online. Important The procedure to handle a damaged local disk of an instance varies based on the instance type. For specific instance types, the instance must be restarted and the damaged local disk must be isolated. For other instance types, the damaged local disk can be isolated online and repaired. | We recommend that you select an appropriate point in time to authorize the damaged disk to be isolated and restart the associated instance after the disk is isolated. In this case, the local disk is isolated offline, so you must restart its associated instance for the isolation operation to take effect. Note For more information, see the "Scenario ③" section in O&M scenarios and system events for instances equipped with local disks. |
| Re-initialization of damaged local disks and instance restart due to system maintenance | SystemMaintenance.RebootAndReInitErrorDisk | Critical |
| This system event is immediately triggered when Alibaba Cloud detects a hardware or software damage in a local disk of an instance and fails to restore the local disk online. Important The procedure to handle a damaged local disk of an instance varies based on the instance type. For specific instance types, the instance must be restarted and the damaged local disk must be isolated. For other instance types, the damaged local disk can be isolated online and repaired. | We recommend that you select an appropriate point in time to authorize the local disk to be restored and restart the associated instance after the disk is restored. In this case, the local disk is restored offline, so you must restart its associated instance for the restoration operation to take effect. Note For more information, see the "Scenario ③" section in O&M scenarios and system events for instances equipped with local disks. |
| In-place repair of instance equipped with local disks | SystemMaintenance.StopAndRepair | Critical |
| This system event is triggered 48 to 168 hours before the scheduled time of system maintenance when Alibaba Cloud detects a risk of hardware failure in the underlying host of an instance. | We recommend that you select an appropriate period of time to authorize Alibaba Cloud to repair or redeploy the instance that is equipped with local disks. Note For more information, see O&M scenarios and system events for instances equipped with local disks. |
Unexpected O&M events
| Event description | Event name | Event severity | CloudMonitor event | Time when a system event is triggered | Handling suggestion |
|---|---|---|---|---|---|
| Instance restart due to a system error | SystemFailure.Reboot | Critical |
| This system event is immediately triggered when Alibaba Cloud detects that an instance is restarted due to hardware or software failure in the underlying host. | We recommend that you wait for the instance to be automatically restarted and then check whether the instances and applications continue to work as expected. Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Instance restart due to an instance error | InstanceFailure.Reboot | Critical |
| This system event is immediately triggered when Alibaba Cloud detects that an instance is restarted due to a kernel panic in the operating system of the instance. | We recommend that you wait for the instance to be automatically restarted and then check whether the instances and applications continue to work as expected. You can troubleshoot and prevent the error based on the system logs and screenshots of the instance. For more information, see View system logs and screenshots. |
| Instance stop due to a system error | SystemFailure.Stop | Critical |
| This system event is immediately triggered when Alibaba Cloud detects that an instance is stopped due to hardware or software failure in the underlying host. | We recommend that you wait for the instance to be automatically stopped. Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Instance redeployment due to a system error | SystemFailure.Redeploy | Critical |
| This system event is immediately triggered when Alibaba Cloud detects hardware or software failure in the underlying host of an instance equipped with local disks and the instance must be redeployed. Note Only instances that depend on host hardware support this system event, such as instances that are equipped with local disks or support SGX encrypted computing. | We recommend that you make preparations such as modifying the /etc/fstab configuration file and backing up data, and then take one of the following actions in response to the event:
Note You can modify the maintenance attributes of the instance to specify the default action to take when the instance encounters a maintenance event. For more information, see Modify instance maintenance attributes. |
| Instance release due to a creation failure | SystemFailure.Delete | Critical |
| This system event is immediately triggered when Alibaba Cloud detects that an instance you order cannot be created. | We recommend that you wait for the instance to be automatically released. Typically, an instance is automatically released within 5 minutes when the instance cannot be created. Note If you have paid for the order, the payment is refunded after the instance is released. To ensure that instances can be created, we recommend that you take the following actions:
|
| Damage alert generated for local disks | ErrorDetected | Critical |
| This system event is immediately triggered when Alibaba Cloud detects a hardware or software damage in a local disk of an instance. | We recommend that you make preparations such as modifying the /etc/fstab configuration file and backing up data, and then have the damaged local disk isolated and restored when appropriate. Note For more information, see the "Scenario ③" section in O&M scenarios and system events for instances equipped with local disks. |
| Disk performance significantly affected | Stalled | Critical |
| This system event is immediately triggered when Alibaba Cloud detects that the performance of cloud disks on an instance is significantly affected. | We recommend that you isolate reads and writes on the disk at the application layer or disassociate the ECS instance from the associated Server Load Balancer (SLB) instance. |
| Trusted Platform Module (TPM) security alert | Security.TpmAlert | Warning |
| This system event is immediately triggered when Alibaba Cloud detects an exception about the trusted system on a security-enhanced instance. | We recommend that you view event details in the ECS console to identify the exception cause and troubleshoot the exception. For more information, see Handle trusted exceptions. |
Instance migration events due to upgrades at the underlying layer
| Event description | Event name | Event severity | CloudMonitor event | Time when a system event is triggered | Handling suggestion |
|---|---|---|---|---|---|
| Instance migration due to upgrades at the underlying layer | SystemUpgrade.Migrate | Critical | Undefined | This system event is triggered when instances are affected by the upgrades and improvements of physical infrastructure in regions and zones where these instances resides. | We recommend that you view event details in the ECS console and migrate affected instances as instructed. For more information, see Instance migration due to upgrades at the underlying layer. |
Performance limited events of burstable instances
| Event description | Event name | Event severity | CloudMonitor event | Time when a system event is triggered | Handling suggestion |
|---|---|---|---|---|---|
| Burstable instance performance limited to the baseline level due to insufficient CPU credits | Undefined | Warning | Instance:BurstablePerformanceRestricted | This system event is triggered when all accrued CPU credits of a burstable instance are consumed. | We recommend that you take one of the following actions in response to the event:
If you want to specify thresholds for triggering notifications about this event, for example, if you want an event notification to be sent when accrued CPU credits remain less than 10 for consecutive 10 minutes, you can configure event-triggered alert rules for the event in the CloudMonitor console. For more information, see Monitor burstable instances. |
State change events
| Event description | Event name | Event severity | CloudMonitor event | Time when a system event is triggered | Handling suggestion |
|---|---|---|---|---|---|
| Preemptible instance interruption | Undefined | Warning | Instance:PreemptibleInstanceInterruption | This system event is triggered 5 minutes before a preemptible instance is reclaimed. | We recommend that you take one of the following actions:
|
| Performance mode change of burstable instances | Undefined | Warning | Instance:PerformanceModeChange | This system event is triggered when a burstable instance switches between the unlimited and standard modes. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Instance state change | Undefined | Notification | Instance:StateChange | This system event is triggered when the state of an instance changes, such as from Running to Stopping and from Stopping to Stopped. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Automatic instance reactivation | Undefined | Notification | Instance:AutoReactivateCompleted | This system event is triggered when an instance is automatically reactivated while overdue payments in your account are settled. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Hot migration of instances between dedicated hosts | Undefined | Notification | Instance:LiveMigrationAcrossDDH | This system event is triggered when an instance is hot migrated between dedicated hosts. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Disk operations completed | Undefined | Notification | Disk:DiskOperationCompleted | This system event is triggered when a pay-as-you-go disk is manually attached or detached. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Disk billing method change from subscription to pay-as-you-go | Undefined | Notification | Disk:ConvertToPostpaidCompleted | This system event is triggered when a subscription disk is changed to a pay-as-you-go disk. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |
| Disk snapshot created | Undefined | Notification | Snapshot:CreateSnapshotCompleted | This system event is triggered when a snapshot is created for a disk. | We recommend that you determine whether to follow the event. If you want to follow the event, you can configure notifications about the event in the CloudMonitor console. For more information, see Configure event notifications. |