After deploying an application on SAE, you can manage its lifecycle by updating, scaling, starting, stopping, deleting, and monitoring it.
Operation Entry Point
Log on to the SAE console. In the navigation pane on the left, choose . Select the target region and namespace. Then, click the target application name.
View application basic information
On the Basic Information page, you can view and manage all key application information. The details are as follows:
Metering data
In the Metering Data section, you can view metrics such as Month-to-Date CU Usage, CPU Resource Usage This Month, Memory Resource Usage This Month, Real-time CPU Resource Usage, and Real-time Memory Resource Usage. You can analyze this data to better manage and optimize resource allocation.
Application information
In the Application Information section, you can view basic details such as the application name, namespace, and application ID. You can modify the Instance Type, update the Security Group, change the vSwitch, and manage Application Tags and the Application Description. For more information, see the documents in the Application O&M category.
In the Application Access Settings section, you can control and manage how external users access applications deployed on SAE. Two access methods are available:
CLB-based Access: You can attach a public CLB to enable Internet access to SAE applications. Alternatively, you can attach a private CLB for inter-application communication within the same VPC. For more information, see Bind a CLB instance to an application, and generate a public or private IP for it.
K8s Service-based Access: You can view the Service Name, Port, and Protocol.
In the Gateway Routing Settings section, you can add a forwarding rule. For more information, see the documents in the Configure gateway routing (Ingress) for application access category.
Instance list
On the Instance List tab, you can view all application instances created under this service. Each instance represents an independently running application environment. You can view each application's instance ID, vSwitch, and IP address. You can manage these instances by viewing real-time logs, checking events, and deleting them. This helps you efficiently manage and maintain your serverless applications. For more information, see the documents in the Application O&M category.
Auto Scaling
On the Auto Scaling tab, you can view the Change Trend of Instance Quantity with Scaling Metrics to gauge resource utilization. For more information, see Observable scaling policy. You can add auto scaling policies or enable idle mode to optimize cost efficiency and performance. For more information, see Configure an auto scaling policy and Idle mode (invitational preview).
View application configuration
On the Basic Information page, click View Application Configuration. In the View Current Configuration Information dialog box, you can view the application's detailed configuration.
View application status
On the Basic Information page, you can view and modify the application's start/stop status. For more information, see Start or stop an application.
Update applications
The entry points for operations vary depending on the scenario.
Change a running application
After you redeploy an application, the application is restarted. To prevent unpredictable errors such as business interruptions, we recommend that you deploy applications during off-peak hours.
On the SAE Application List page, select a destination region and namespace in the top navigation bar. Click the ID of the target Application to open the application details page.In the navigation pane on the left, click Basic Information. In the upper-right corner, click Deploy Application.
Change a stopped application
On the SAE Application List page, select a destination region and namespace in the top navigation bar. Click the ID of the target Application to open the application details page.Click Basic Information, and then click Modify Application Configuration.
If the application has more than one instance, you must select a release policy to publish the updated application:
Roll back to historical versions
On the Basic Information page, click Roll Back to Historical Version. On the Roll Back to Historical Version page, you can select a version and set the release policy. For more information, see Roll back an application to a previous version.
Manually scale applications
On the Basic Information page, click Manual Scaling. For more information, see Manually scale instances.
If the total number of instances after scaling out exceeds the application's resource usage limit, the scale-out operation fails. To add more application instances, you can join the DingTalk group (DingTalk group ID: 32874633) to request a quota increase.
If your scaling is not urgent, you can use auto scaling policies.
Automatically scale applications
On the Basic Information page, on the Auto Scaling tab, click Add Auto Scaling Policy in the Auto Scaling section. For more information, see Configure an auto scaling policy.
Start or stop applications
The steps to start or stop a single application are as follows. For steps to start or stop multiple applications, see One-click start and stop applications.
Stop Application: On the Basic Information page, click Stop Application. In the Prompt dialog box, click Confirm to stop the application.
You can stop a running application at any time, as needed. When you stop an application, its minimum number of active instances is set to 0, and the instance count is set to 0. The compute resources it uses stop billing or metering.
WarningAfter the application stops, if it relies on other products or services during runtime, such as attached SLB instances or VPCs, those products or services remain in a billing state.
Start Application: On the Basic Information page, click Start Application. In the Start Application dialog box, click Confirm to start the stopped application.
You can start a stopped application at any time, as needed. After the application starts, the number of instances is restored to the value configured before it stopped. Billing or metering for compute resources resumes.
Restart applications
For a running application instance, on the Basic Information page, choose . In the Restart Application dialog box, follow the on-screen prompts.
If an auto scaling policy is enabled, set Resume Auto Scaling After Application Restart. Then, click Confirm.
If no auto scaling policy is enabled, set Minimum Active Instances. Then, click Confirm.
If the application runs normally but the business experiences issues, do not manually restart the entire application. First, use the health check feature to diagnose the application instance status. If the check shows an unhealthy instance, the system automatically restarts it. For more information, see Configure application health checks.
Delete applications
On the Basic Information page, choose . In the Delete Application dialog box, click Confirm to delete the deployed application.
If your application relies on other products or services during runtime, such as attached CLB instances or configured VPCs, confirm whether you still need those dependent products or services before deleting the application. If not, stop the service to halt billing.
Enable or disable application monitoring
On the Basic Information page, you can enable or disable application monitoring. For more information, see Enable or disable application monitoring for an application.
Enable Application Monitoring: Click . In the Enable Application Monitoring dialog box, click Confirm to enable application monitoring.
Disable Application Monitoring: Click . In the Disable Application Monitoring dialog box, click Confirm to disable application monitoring.