All Documents
Current Document
Content is empty
If you don't find the content you expect, please try another search term
Found 0 result in total
Content is empty
If you don't find the content you expect, please try another search term
Last updated：2022-01-21 15:39:09
System events are unexpected underlying events or scheduled underlying maintenance events that affect the running status of Kingsoft Cloud Elastic Compute (KEC) instances. System events occur when KEC instances are restarted, stopped, or released due to the failure of underlying hosts. System events do not include routine maintenance and seamless failover. KEC supports sending you notifications and event information, such as the event cycle, when or before system events affecting your KEC instance occur. You can subscribe to system event notifications to get to know system events and take countermeasures in a timely manner. For unexpected underlying events, KEC will notify you of their occurrence and impact so that you can get to know and respond to them in a timely manner. For scheduled system events, KEC will notify you of their scheduled execution time and impact on your instances so that you can back up data in advance. You can also query system events in the last 30 days for monthly data review and troubleshooting.
| Event type | Event type parameter | Event name | Event name parameter | Description |
| Elastic Block Stroage (EBS) volume-based KEC instance reboot | InstanceReboot | |||
| Start of EBS volume-based EKC instance reboot | InstanceRebootStart | When the host of an EBS volume-based KEC instance fails, the instance automatically recovers. In this case, you must migrate your business to another KEC instance and reboot the new business instance. | Failure of EBS volume-based KEC instance reboot | InstanceRebootFailed | Completion of EBS volume-based KEC instance reboot | InstanceRebootExecuted |
| Local disk-based KEC instance reboot | LocalDiskInstanceReboot | |||
| Start of local disk-based KEC instance reboot | LocalDiskInstanceRebootStart | When the host of a local disk-based KEC instance fails, the KEC instance automatically recovers. In this case, you must migrate your business to another KEC instance and reboot the new business instance. | Failure of local disk-based KEC instance reboot | LocalDiskInstanceRebootFailed | Completion of local disk-based KEC instance reboot | LocalDiskInstanceRebootExecuted |
| Hardware damage of a local directly-connected disk-based KEC instance | LocalDiskServerErrorDetected | |||
| Scheduling of hardware repair for a local directly-connected disk-based KEC instance | LocalDiskServerErrorRepairTimeScheduled | When the local directly-connected disk or other hardware of the host of a KEC instance fails, you must stop the KEC instance on the host and replace the hardware. | Start of hardware repair for a local directly-connected disk-based KEC instance | LocalDiskServerErrorRepairStart | Failure of hardware repair for a local directly-connected disk-based KEC instance | LocalDiskServerErrorRepairFailed | Completion of hardware repair for a local directly-connected disk-based KEC instance | LocalDiskServerErrorRepairExecuted |
The following table describes the status in the lifecycle of a system event.
| Status code | Event status | Description |
| Start | Start | The event has started, which is an intermediate state. |
| TimeScheduled | Scheduling of time | The execution time is scheduled, which is an intermediate state and applicable to scheduled events. |
| Executed | Completion | The event is completed, which is a final state. |
| Failed | Failed | The event failed after a number of attempts, which is a final state. |
After you subscribe to KEC system events in Kingsoft Cloud Monitor Service (CMS), you can query system events for KEC instances and local disks in the last 30 days and perform custom O&M operations in the KEC console.
Procedure
Pure Mode
