Cloud Monitor provides basic monitoring of IT infrastructure, monitoring of dial testing for public network quality, and business monitoring based on events, custom metrics, and logs. After you integrate Cloud Monitor with Function Compute, you can use various events to trigger custom functions so that you can implement automatic processing of more cloud resources.
Scenarios
You can use Cloud Monitor triggers to implement automatic processing of an instance that is restarted due to system or instance errors. For example, after an Elastic Compute Service (ECS) instance is restarted, a function can be triggered by Cloud Monitor to search for disks that are attached to the ECS instance and create snapshots for the disks.
Event types
Impact | Event type | Parameter | Recommended solution |
---|---|---|---|
Instance restart | Instance restart due to scheduled system maintenance | SystemMaintenance.Reboot | Select an appropriate point in time during the user operation window to perform the
following operations:
|
Unexpected instance restart | Instance restart due to an unexpected system error | SystemFailure.Reboot | For more information, see Automatic recovery events of instances. |
Instance restart due to an unexpected instance error | InstanceFailure.Reboot | If you receive an event notification during or after the instance restart, we recommend
that you:
|
|
Instance redeployment | Instance redeployment due to scheduled system maintenance | SystemMaintenance.Redeploy | For more information, see Redeploy an instance equipped with local disks. |
Instance redeployment due to a system error | SystemFailure.Redeploy | For more information, see Redeploy an instance equipped with local disks. | |
Instance stop | Subscription instance: instance stop upon expiration | InstanceExpiration.Stop | Renew the instance. For more information, see Renewal overview. |
Pay-as-you-go instance: instance stop due to overdue payments | AccountUnbalanced.Stop |
We recommend that you maintain a sufficient balance for your payment account to prevent instances from being stopped due to insufficient account balance. |
|
Instance release | Subscription instance: instance release after expiration | InstanceExpiration.Delete | Renew the instance. For more information, see Renewal overview. |
Pay-as-you-go instance: instance release due to overdue payments | AccountUnbalanced.Delete |
We recommend that you maintain a sufficient balance for your payment account to prevent instances from being stopped due to insufficient account balance. |
|
Instance release | Instance release due to a creation failure | SystemFailure.Delete | For more information, see System event of instance creation failure. |
Impacts on disk performance | Severe impacts on disk performance | Stalled | On the application layer, isolate read and write operations on the disk or temporarily remove the ECS instance from the backend server group of the SLB instance. |
Damages to local disks | Damages to local disks | ErrorDetected | For more information, see Overview of system events on ECS instances equipped with local disks. |
Instance restart and isolation of the damaged local disk | Instance restart and isolation of the damaged local disk due to scheduled system maintenance | SystemMaintenance.RebootAndIsolateErrorDisk | For more information, see Isolate damaged local disks by using Alibaba Cloud CLI. |
Instance restart and restoration of the damaged local disk | Instance restart and re-initialization of the damaged local disk due to scheduled system maintenance | SystemMaintenance.RebootAndReInitErrorDisk | For more information, see Isolate damaged local disks by using Alibaba Cloud CLI. |
Disk detachment error | Removal of residual disks due to system maintenance | SystemMaintenance.CleanInactiveDisks | Log on to the ECS console, view pending events, and handle the event as instructed. For more information, see View system events. |
Limited performance of burstable instances | The performance of burstable instances below the baseline performance due to insufficient available CPU credits | N/A | You can use one of the following methods to handle the event:
|
Isolation of the damaged local disk | Isolation of the damaged local disk due to system maintenance | SystemMaintenance.IsolateErrorDisk | For more information, see Isolate damaged local disks by using Alibaba Cloud CLI. |
Recovery of the local disk | Re-initialization of the damaged local disk due to system maintenance | SystemMaintenance.ReInitErrorDisk | For more information, see Isolate damaged local disks by using Alibaba Cloud CLI. |
References
For more information about system events, see Overview.