After you perform lifecycle operations 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 time consumed by each sub-step.
View current change status
When you create or modify an application, you can view the details of its release record. This topic uses an application deployment as an example.
In the SAE Applications list, select the target 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 configuration and set the release policy as needed, and then click OK.
At the top of the Basic Information page, click Change Details to view information about the current change.
The Change Details page displays the following information:
Change process ID, number of release batches, processing method between batches, execution status (such as Waiting for manual confirmation), change type, and release time.
Descriptive information, such as the deployment method (for example, batched canary release), version number, package name, and change target.
Action buttons: Rollback Now, Terminate Release, and Refresh.
Tabs for each batch, such as Canary Change and First Batch after Canary. After the current batch is complete, you can click Start Next Batch to continue the release.
Below each batch, a timeline view shows the progress of the deployment workflow. This view includes the execution status and time consumed by steps such as building the image, initializing the environment, creating or updating the deployment configuration, executing the application deployment, and releasing instances.
For more information about the details in a release record, see Release record time consumption visualization.
View historical change records
In the SAE Applications list, select the target region and namespace at the top. Then, click the target Application ID to open the application's details page.
In the left-side navigation pane, click Change Records to view all release records. For more information about the details of a release record, see Release records.
Select a release record type: Click the drop-down list next to Number of Release Records to select a specific type.
NoteThe default type is Deploy Application.
View change details of a release record: In the Actions column of the target release record, click Change Details to view its details.
NoteRelease records are stored for a maximum of three months.
Release records
Page overview
Release Record Type: From the dropdown list next to Number of Release Tasks, you can filter by release record type to view the number of successful and failed release records for that type.
Time consumed by release records: You can view the average and maximum time consumed by release records of the same type.
Top 5 sub-steps by time consumed: A release record consists of multiple sub-steps. The system identifies the five sub-steps that take the longest on average 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 details about the release record sub-steps, see Release record time consumption visualization.
Release record time consumption visualization
Note the following points:
Release record sub-steps are divided into two categories:
Platform: Sub-steps related to the platform appear in black text.
User: Sub-steps related to the user appear in blue text.
Analysis of time consumption: You can view the time consumed by 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, a corresponding error message is displayed for the relevant sub-step. You can then modify the application configuration accordingly and redeploy the application.
For a detailed description of the release record sub-steps, see the following table.
Sub-step
Category
Description
Build Image
Platform-side
When you deploy an application by using a code package, the system builds an image from your uploaded code package and pushes it to a private Alibaba Cloud image repository.
NoteThe system creates and manages this image repository automatically.
Initialize Environment
Platform-side
This step confirms the namespace required to create the SAE application and ensures that environment resources are ready.
Create Or Update Deployment Configuration
Platform-side
This step creates or updates the application's basic configurations, such as the image address, resource specifications, and policies.
Execute Deployment Steps
Platform-side
This step starts the application deployment task, which includes network configuration and resource pre-allocation.
Release Instances
Platform-side
This step creates instances (pods). This includes steps such as resource scheduling, volume mounting, init container startup, image pulling, and container startup. If there are multiple instances, the system creates them 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 for CPU, memory, and network configuration.
The system then binds the application instance to the resource node.
After the application instance is successfully bound to the resource node, this binding completes the resource allocation and configuration process.
Instance is being prepared
Platform-side
The resource node reserves resources for the application instance and prepares its runtime environment. This includes platform-side operations such as network initialization, storage initialization, and init container initialization.
An image starts to be pulled from a repository.
Platform-side
The system pulls the application image from the private image repository.
Deployment with an image: The application image is pulled based on the image address.
Deployment with a code package: The image address is in the format
Image Source/Image Repository Name/Image Tag.
An image is successfully pulled from a repository.
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 creation fails, an error message appears.
Container is Started
User-side
The application container process starts successfully. If startup fails, an error message appears.
Instance Ready
User-side
The application instance passes the health check and is ready to process client traffic.
Error examples
If an error occurs during application creation or deployment, an error message is displayed for the corresponding release record sub-step. The following sections provide specific examples.
Health check failure example
You can view the error message in the following two ways.
Method 1:
View the error message in the release record sub-step.
In the event timeline, the Health check failed event displays the error message:
Liveness probe failed: Trying 127.0.0.1... check port 30000 failed, reason: failed: dial tcp 127.0.0.1:30000: connect: connection refused. This indicates that the container's liveness probe failed because the connection to port 30000 was refused. This event appears between the Container Running (Succeeded) and Instance Ready (Succeeded) events.Method 2:
View the error message in Application Events.
In Application Events, a Warning-level Unhealthy event appears with the error message:
Liveness probe failed: Trying 127.0.0.1... check port 30000 failed
Error handling example
The instance fails to start due to a liveness probe failure.
Possible causes
The port is incorrectly configured for the health check.
The network configuration is incorrect.
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.