After you deploy an application on SAE, you can manage the lifecycle of the application. For example, you can update, start, stop, and delete the application. You can also scale in or scale out the instances for the application.
Procedure
Log on to the SAE console. In the left-side navigation pane, choose . On the page that appears, select a region in the top navigation bar and a namespace from the Namespace drop-down list, and click the name of the desired application.
View the basic information of an application
On the Basic Information page, you can view and manage all key configurations of an application. Below is a table that describes these details:
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. This helps you optimize resource allocation.
Application information
In the Application Information section, you can view basic details such as the application name, namespace, and application ID. Additionally, you can modify the Instance Type, update the Security Group, change the vSwitch, and manage Application Tag 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 the access of external users to applications deployed on SAE. Two methods of access are available:
CLB-based Access: To enable Internet access to SAE applications, you can attach a public CLB. Alternatively, attaching a private CLB allows for inter-application communication within the same VPC. For more information, see Bind an SLB instance to an application.
NLB-based Access: You can view the Instance ID, Port, and Protocol.
In the Gateway Routing Settings section, you can Add Forwarding Policy. For more information, see the documents in the Configure gateway routing (Ingress) for application access category.
Instances
On the Instances tab, you can view all application instances associated with the service. Each instance is an independent application environment. On this tab, you can also view instance ID, vSwitch, and IP address of each instance. Additionally, you can manage these instances with operations including viewing real-time logs, monitoring events, and deleting instances. This facilitates efficient management and maintenance of your serverless applications. For more information, see the documents in 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. Additionally, you can add auto scaling policies or enable idle mode for optimal cost efficiency and performance. For more information, see Configuring Auto Scaling policy and Idle mode (invitational preview).
View the configurations of an application
In the upper-right corner of the Basic Information page, click View Application Configurations. In the View Current Configurations dialog box, view the configuration details of the application.
View application status
On the Basic Information page, you can view and modify the status of an application. For more information, see Start or stop an application.
Update an application
The procedure varies in different scenarios:
Modify running applications
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.
Log on to the SAE console. In the left-side navigation pane, choose . On the page that appears, select a region in the top navigation bar and a namespace from the Namespace drop-down list, and then click the desired application name.
On the Basic Information page of the application, click Deploy Application.
Modify stopped applications
Log on to the SAE console. In the left-side navigation pane, choose . On the page that appears, select a region in the top navigation bar and a namespace from the Namespace drop-down list, and then click the desired application name.
On the Basic Information page of the application, click Modify Application Configurations.
If the number of instances in the application is greater than 1, select a release policy to release the updated application:
Roll back an application to an earlier version
In the upper-right corner of the Basic Information page, click Back to Earlier Version. On the Back to Earlier Version page, select a version and configure a release policy. For more information, see Roll back an application to a previous version.
Manually scale in or scale out the instances for an application
In the upper-right corner of the Basic Information page, click Manual Scaling. For more information, see Manually scale instances.
If the total number of the original instances and the instances that you want to add exceeds the upper limit on the number of application instances, the scale-out operation fails. If you want to add additional application instances, join the DingTalk group 32874633 to apply to increase the quota.
If you are not urgent to scale in or scale out your instances, we recommend that you use the auto scaling feature. For more information, see Configure an auto scaling policy.
Automatically scale in or scale out the instances for an application
On the Instance Deployment Information tab of the Basic Information page, click + Add Auto Scaling Policy in the Auto Scaling section. For more information, see Configure an auto scaling policy.
Start or stop an application
This section describes the procedures for starting and stopping an application. For guidance on managing multiple applications simultaneously, see Use the one-click start and stop feature to manage applications.
Stop Application: In the upper-right corner of the Basic Information page, click Stop Application. In the Note message, click OK to stop the application.
You can stop a running application at any time based on your business requirements. After you stop an application, the system automatically sets the minimum number of available instances of the application to 0 and the number of instances to 0. In this case, the system pauses billing or calculating the number of computing resources that are used by the application.
WarningIf your application depends on other cloud services or resources during runtime, such as Server Load Balancer (SLB) instances and virtual private clouds (VPCs), you are still charged for using the services or resources after the application is stopped.
Start Application: In the upper-right corner of the Basic Information page, click Start Application. In the Note message, click OK to start the application that is in the stopped state.
You can start a stopped application at any time based on your business requirements. After you start an application, the number of instances is restored to the value that is specified before the application is stopped. In this case, the system resumes billing or calculating the computing resources that are used by the application.
Restart an application
In the upper-right corner of the Basic Information page of an application that is in the running state, choose . In the Restart Application dialog box, configure the parameters as prompted.
If an auto scaling policy is enabled, configure the Resume Auto Scaling After Application Restart parameter and click Confirm.
If no auto scaling policy is enabled, configure the Minimum Available Instances parameter and click Confirm.
If an application runs as expected but your business is not running as expected, do not manually restart the application. You must use the health check feature to check the health status of the instances in the application. If the check result indicates that an instance is unhealthy, the system automatically restarts the instance. For more information, see Configure application health checks.
Delete an application
In the upper-right corner of the Basic Information page, choose . In the Delete Application message, click OK to delete the application.
If your application depends on other cloud services or resources during runtime, such as SLB instances and VPCs, check whether you need to continue using the services or resources before you delete the application. If you no longer need to use a service or a resource, you can deactivate the service or disable the resource. Then, the billing for the service or resource is stopped.
Enable or disable the application monitoring feature for an application
In the upper-right corner of the Basic Information page, enable or disable the application monitoring feature. For more information, see Enable or disable application monitoring for an application.
Enable Application Monitoring: choose . In the Note message, click OK to enable the application monitoring feature.
Disable Application Monitoring: choose . In the Note message, click OK to disable the application monitoring feature.