After you host an application on SAE, you can manage the application lifecycle, including updating, scaling, starting, stopping, deleting, and enabling or disabling application monitoring.
Procedure
Log on to the SAE console. In the left-side navigation pane, choose . Select the target region and namespace, and then click the name of the target application.
View basic application information
On the Basic Information page, you can view and manage your application's key information.
Metering
In the Metering section, you can view 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. Analyze this data to optimize your 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 also change the instance type, change the security group, change the vSwitch, and manage the Application tag and Application description. For more information, see Application O&M.
-
In the Application access settings section, SAE provides two methods for managing external access to applications deployed on SAE:
-
CLB-based access: You can bind a public-facing CLB to allow internet access to your SAE application, or bind a private CLB to enable communication between all applications within the same VPC. For more information, see Bind a CLB instance for public or private access.
-
Kubernetes service-based access: You can view the Service name, port, and protocol.
-
-
In the Gateway routing settings section, you can Add forwarding policy. For more information, see configuring gateway routing (ingress).
Instances
The Instance list tab displays all application instances created for the service. Each instance represents an independent running environment. You can view information for each instance, such as its ID, vSwitch, and IP address. You can also manage instances by viewing real-time logs, checking events, and deleting them. For more information, see Application O&M.
Autoscaling
On the Autoscaling tab, you can view a trend chart of how the instance count varies with scaling metrics to understand resource usage. For more information, see Observable Scaling. You can also add an autoscaling policy or enable idle mode to optimize cost and performance. For more information, see Configure autoscaling policies and Idle mode (invitational preview).
View application configuration
On the Basic Information page, click View application configuration. The View current configuration dialog box displays the detailed configuration of the application.
View application status
On the Basic Information page, you can view the application's status and modify it as needed. For detailed instructions, see Start or stop an application.
Update an application
The entry point varies by scenario:
Running application
Redeploying an application restarts it. To avoid service interruptions or other unexpected issues, perform deployments during off-peak hours.
In the SAE Application List, select the target region and namespace at the top, and then click the target application ID to go to the application details page. In the left-side navigation pane, click Basic Information, and then click Deploy application in the upper-right corner.
Stopped application
In the SAE Application List, select the target region and namespace at the top, and then click the target application ID to go to the application details page. Click Basic Information, and then click Modify application configuration.
If the application has more than one instance, you can choose one of the following release policies to deploy the updated application:
Roll back to a previous version
On the Basic Information page, click Back to earlier version. On the Back to earlier version page, select a version and set a release policy. For detailed instructions, see Roll back to a previous version.
Manually scale an application
On the Basic Information page, click Manual scaling. For detailed instructions, see Manually scale instances.
-
When you scale out, the operation fails if the total number of instances (both existing and new) exceeds the resource quota for your application. To add more instances, join the DingTalk group (ID: 32874633) to request a quota increase.
-
If your scaling needs are not urgent, we recommend that you configure an autoscaling policy.
Automatically scale an application
On the Basic Information page, go to the Autoscaling tab and click Add elasticity policy in the autoscaling section. For detailed instructions, see Configure autoscaling policies.
Start or stop an application
The following steps describe how to start or stop a single application. For instructions on managing multiple applications, see Start or stop multiple applications.
-
Stop an application: On the Basic Information page, click Stop application. In the Note dialog box that appears, click OK to stop the application.
You can stop a running application at any time based on your business requirements. When an application is stopped, its minimum number of available instances and its instance count are set to 0. Billing and metering for its computing resources stop.
WarningIf your application depends on other products or services, such as SLB instances and VPC resources, these services continue to incur charges after the application is stopped.
-
Start an application: On the Basic Information page, click Start application. In the Start Application dialog box that appears, click OK to start the application.
You can start a stopped application at any time. When the application starts, the number of instances returns to the value configured before the application was stopped, and resource metering or billing resumes.
Restart an application
To restart a running application, on the Basic Information page, choose . In the Restart Application dialog box that appears, follow the on-screen instructions.
-
If an autoscaling policy is enabled: Set the Resume autoscaling after application restart option and click OK.
-
If no autoscaling policy is enabled: Set the Minimum available instances and click OK.
If the application is running normally but your service is experiencing issues, do not manually restart the entire application. First, use the health check feature to diagnose the status of the application instances. If the check result indicates that an instance is unhealthy, the instance restarts automatically. For more information, see Configure a health check.
Delete an application
On the Basic Information page, choose . In the Delete Application dialog box that appears, click OK to delete the deployed application.
If your application depends on other products or services, such as CLB instances and VPC resources, confirm whether you need to continue using them before you delete the application. If not, stop those services to avoid further charges.
Enable or disable application monitoring
In the upper-right corner of the Basic Information page, you can enable or disable application monitoring. For detailed instructions, see Enable or disable application monitoring.
-
Enable application monitoring: Choose . In the Enable Application Monitoring dialog box that appears, click OK.
-
Disable application monitoring: Choose . In the Disable Application Monitoring dialog box that appears, click OK.