View change records in Serverless App Engine (SAE) - Serverless App Engine

After you perform lifecycle actions in SAE, such as deploying, starting, scaling out, or scaling in an application, you can view the details of the change record. These details include the sub-steps of the release record and the duration of each sub-step.

View the current change status of an application

When you create or modify an application, you can view the details of its release record. This topic uses application deployment as an example.

In the SAE Applications list, select the destination region and namespace at the top. Then, click the target Application ID to open the application details page.
On the Basic Information page, click Deploy Application. Modify the configurations, set the release policy as needed, and then click OK.
At the top of the Basic Information page, click Change Details to view details about the change.
For more information about the details in the release record, see Release record time consumption visualization.

View historical change records

In the SAE Applications list, select the destination region and namespace at the top. Then, click the target Application ID to open the application details page.
In the left navigation pane, click Change Records to view all release records. For more information about the details in a release record, see Release records.
- Select a release record type: Click the drop-down list next to the release record count to select a specific release record type.
  Note
  The default type is Deploy Application.
- View release record change details: In the Actions column of the target release record, click Change Details to view the change details.
  Note
  Release records are stored for a maximum of three months.

Release records

Introduction to release records

Release record type: You can filter release records by type from the drop-down list next to the Number Of Release Records to view the number of successful and failed release records for each type.
Time consumption of release records: You can view the average and maximum duration for release records of the same type.
Top 5 sub-steps by time consumption: Each release record has multiple sub-steps, and each sub-step has an execution duration. The system calculates the top five sub-steps with the longest average execution time for each release record type. For more information about each sub-step, see Release record time consumption visualization.
Release record details: In the Actions column of a release record, click Change Details to view its details. For more information about the release record sub-steps, see Release record time consumption visualization.

BLbsfotSW2

Release record time consumption visualization

Note the following points:

Release record sub-steps are divided into two categories:
- Platform-side: Sub-steps performed on the platform appear in black font.
- User-side: For platform-side deployments, the font for child steps is blue.
Time consumption analysis: You can view the duration of each sub-step to the right of its name. Some sub-steps run concurrently.
During application creation or modification, if an application configuration error occurs, an error message appears for the relevant sub-step. You can modify the application configuration based on the error message and then redeploy the application.

For more information about the release record sub-steps, see the following table.

Release record sub-step	System operation classification	Description
Build Image	Platform-side	When you deploy an application using a code package, an image is created from your uploaded code package and pushed to an Alibaba Cloud private image repository. Note This image repository is created by the system. You do not need to manage it.
Initialize Environment	Platform-side	Confirms the namespace required to create the SAE application and ensures that environment resources are ready.
Create Or Update Deployment Configuration	Platform-side	Creates or updates the basic configurations of the SAE application, such as the image address, resource specifications, and policies.
Execute Deployment Steps	Platform-side	Starts the application deployment task, which includes network configuration and resource pre-allocation.
Release Instances	Platform-side	Creates instances (pods). This includes steps such as resource scheduling, mounting volumes, starting init containers, pulling images, and starting containers. If there are multiple instances, they are created independently.
Resource Scheduling	Platform-side	The scheduler assigns application instances (pods) to specific resource nodes. This includes the following steps: The system assigns the application instance to a node that meets the application's resource requirements (CPU, memory, and network configuration). The application instance is bound to the resource node. After the application instance is successfully bound to the resource node, resource allocation and configuration are complete.
Instance Preparing	Platform-side	The resource node reserves resources for the application instance and prepares its running environment. This includes platform-side operations such as network initialization, storage initialization, and init container initialization.
Start Pulling Image	Platform-side	Pulls the application image from the private image repository. Image-based deployment: Pulls the application image based on the image address. Code package-based deployment: The image address format is `Image Source/Image Repository Name/Image Tag`.
Image Pull Finished	Platform-side	The application image is pulled successfully. If the pull fails, an error message appears.
Container Created Successfully	User-side	The application container is created successfully. If the creation fails, an error message appears.
Container Process Started	User-side	The application container process starts successfully. If the startup fails, an error message appears.
Instance Ready	User-side	The application instance passes the health check and can process client traffic.

Error examples

If an error occurs during application creation or deployment, an error message appears in the corresponding release record sub-step. The following sections provide specific examples.

Example of a health check failure error

You can view the error message in the following two ways.

Method 1:
View the error message in the release record sub-step of the target release record.
Method 2:
You can view the error message in Application Events.

Example of error handling

The instance fails to start due to a liveness check failure.

Possible causes
- The port is incorrectly configured for the health check.
- There is a problem with the network configuration.
Solution
- Identify the application instance port and confirm that the port is correctly configured for the health check.
- Confirm that the network configuration is correct.