- Documentation
Elastic Compute Service
Elastic Compute Service
Best Practices
Monitoring
Querying and responding to "InfrastructureUpgrade.Redeploy" events
Monitoring
Querying and responding to "InfrastructureUpgrade.Redeploy" events
Querying and responding to "InfrastructureUpgrade.Redeploy" events
This topic describes how to query and respond to "InfrastructureUpgrade.Redeploy" events in the console and through the OpenAPI provided by the platform. This helps you quickly troubleshoot issues and run your cloud products stably.
Scenarios
As business develops and the health status of the host of ECS instances changes, the platform will upgrade the infrastructure that is outdated or has poor performance. In such cases, "InfrastructureUpgrade.Redeploy" events are generated, and you will be notified.
After receiving a notification, you can perform as follows:
warning
- During the O&M period, operations such as shutdown and restart are performed on the instance, which may impact your business. Please select an appropriate O&M time.
- Currently, only General-purpose, Compute-optimized, Memory-optimized, and High Frequency instance families support automatic O&M for "InfrastructureUpgrade.Redeploy" events. If you have not completed O&M authorization or have completed O&M authorization with a scheduled execution time that has not yet arrived, automatic O&M (automatic cancellation) will also be triggered if the instance is resized, powered on, or restarted.
- Select an O&M time window and manually authorize O&M personnel to deploy your instance to a new host. This helps avoid impact on your instance from infrastructure upgrades.
You can also create a scheduled maintenance window to enable automatic authorization. When an "InfrastructureUpgrade.Redeploy" event occurs, VolcanoEngine will be automatically authorized to deploy your instance to a new host. Learn more. - Automatic O&M operations can be triggered by actions, including instance resizing, power-on, or restart. This means that the instance will be automatically deployed to a healthy host to reduce risks and avoid damage to your business and data in time.
In the example provided in this topic, O&M is authorized manually.
Procedure
Respond in the console
This practice uses responding to events on the "Events" page as an example. You can also go to the instance details page to respond. For detailed instructions on the instance details page, see Querying and handling events in the ECS console. - In the left-side navigation pane, select "Maintenance & Monitoring > System Events" to go to the Events page.
- In the top menu bar, select the project and region of the target instance.
- Filter the target event by event ID or time.
In the example provided in this topic, instances that trigger "InfrastructureUpgrade.Redeploy" events are mainly involved. For more event types, see Event type summary. - In the "Actions" column of the target event, click the "Authorize maintenance" button to authorize.
- Select a time window for redeploying the instance and agree to the authorization.
- Click the "Confirm" button to complete the authorization.
- After successful authorization, the event status turns Executing.
- O&M personnel will redeploy the instance based on the maintenance time window you specify. After the deployment is completed, the event status turns Succeeded.
Respond through OpenAPI
In this section, the Java language interface is used as an example. The following is for your reference on calling OpenAPI interfaces in sequence to query and respond to ECS instance events.
tip
- Relevant interfaces in this section are called through the SDK. Please import the SDK into your project. For details, see SDK overview.
- If you do not want SDK to be introduced, you can create HTTP/HTTPS requests manually. For details, see Calling methods.
- Events of GPU instances in HPC clusters do not support OpenAPI-based responses.
- Call DescribeEventTypes interface to query whether all events triggered by the instance need a response.
In this practice, a response is required to the "InfrastructureUpgrade.Redeploy" event triggered by instance A.
- Call the UpdateSystemEvents interface to respond to "InfrastructureUpgrade.Redeploy" events. This authorizes platform O&M personnel to redeploy instances and resolve faults.
tip
- Only for "InfrastructureUpgrade.Redeploy" event authorization, the OperatedStartAt and OperatedEndAt parameters can be used to change the maintenance time window.
- The OperatedStartAt and OperatedEndAt parameters only support passing in the following time periods:
- event occurrence time ~ event occurrence time + 12h
- event occurrence time + 12h ~ event occurrence time + 24h
- event occurrence time + 24h ~ event occurrence time + 36h
- event occurrence time + 36h ~ event occurrence time + 48h
- event occurrence time + 48h ~ event occurrence time + 60h
- event occurrence time + 60h ~ event occurrence time + 72h
- Call DescribeSystemEvents interface, pass in the responded event ID to query the current status of the event and other information.
- Response example of an event in Executing status:
- Response example of an event in Succeeded status:
Last updated: 2026.06.18 17:49:51