Serverless App Engine (SAE) integrates with Application Real-Time Monitoring Service (ARMS) to provide multiple monitoring features. With ARMS monitoring enabled, you can locate faulty and slow APIs, detect memory leaks, and identify system bottlenecks — reducing the time you spend diagnosing production issues.
This topic covers how to enable or disable application monitoring and how to manage probe versions, including bulk updates across multiple applications.
Which edition are you on?
SAE offers two editions with different default monitoring behaviors:
| Edition | Default monitoring | To use Premium monitoring |
|---|---|---|
| Professional Edition | No monitoring by default — must be enabled manually | Included at no extra charge |
| Standard Edition | Basic application monitoring, enabled automatically after deployment | Enable Premium monitoring (additional charges apply — see ARMS billing) |
To confirm your edition, check the edition label next to your application on the SAE Application List page.
Resource overhead
When you enable monitoring on a Professional Edition application, SAE injects a built-in monitoring agent into each instance. The agent consumes approximately 0.2 CPU cores and 200 MB of memory per instance. Plan your instance resources to accommodate this overhead before enabling monitoring.
Prerequisites
Before you begin, ensure that you have:
An SAE application (Professional or Standard Edition)
Sufficient instance resources if enabling monitoring on Professional Edition (0.2 CPU cores and 200 MB memory per instance)
For image-based deployments: the probe pre-installed in your custom image (see Install the probe for a Golang application or Install the probe for a Python application)
Enable application monitoring
Professional Edition applications
Professional Edition applications do not enable monitoring by default. Enable it when you create or update the application.
Step 1: Open the monitoring configuration
Choose one of the following entry points depending on your situation:
Create an application: On the SAE Application List page, select a region and namespace, then click Create Application. On the Application Basic Information page, configure the parameters and click Next: Advanced Settings.
Update a running application: On the SAE Application List page, select a region and namespace. Click the application ID to open the details page. In the navigation pane, click Basic Information, then click Deploy Application in the upper-right corner.
WarningRedeploying restarts the application. Perform this operation during off-peak hours to avoid business interruptions.
Update a stopped application: On the SAE Application List page, select a region and namespace. Click the application ID to open the details page. Click Basic Information, then click Modify Application Configuration.
Step 2: Enable monitoring
Find and expand the Application Monitoring section, then turn on the monitoring switch.
Deployment method affects probe installation:
Image deployment: Manually install the probe when building your custom image. For a Golang application, see Install the probe for a Golang application. For a Python application, see Install the probe for a Python application.
Code package deployment: No extra steps required — SAE automatically integrates the probe when building the image from your code package.
Step 3: Complete deployment
Proceed through the remaining configuration steps and complete the application deployment.
Standard Edition applications
Standard Edition applications automatically enable Basic application monitoring after deployment — no extra configuration is required.
To use Premium application monitoring, enable Premium monitoring. Note that Premium monitoring incurs additional charges.
Disable application monitoring
Professional Edition applications
On the Basic Information page of the target application, click Deploy Application.
Find and expand the Application Monitoring section, then turn off the monitoring switch.
Click OK.
Standard Edition applications
On the Basic Information page of the target application, click More in the upper-right corner, then click Stop Application Monitoring.
In the Disable Application Monitoring dialog box, click OK.
Manage probe versions
Probe version management is in beta testing and available by invitation only. To request access, contact the technical staff in DingTalk group 32874633.
SAE lets you select which probe version each application uses. This is useful when you want to pin a specific version for stability or upgrade to a newer version for bug fixes.
Update the probe version for a single application
Step 1: Open the probe configuration
Choose one of the following entry points:
Create an application: On the Application Basic Information page, configure the parameters and click Next: Advanced Settings.
Update a running application: On the SAE Application List page, click the application ID. In the navigation pane, click Basic Information, then click Deploy Application in the upper-right corner.
WarningRedeploying restarts the application. Perform this operation during off-peak hours.
Update a stopped application: On the SAE Application List page, click the application ID. Click Basic Information, then click Modify Application Configuration.
Step 2: Select a probe version
Find and expand the Probe Configuration section, then select the desired Probe Version.
Step 3: Complete deployment
Proceed through the remaining steps and complete the deployment.
Update probe versions in bulk
Use batch operations to update probe versions across multiple applications at once.
Batch probe version management is in beta testing and available by invitation only. Contact DingTalk group 32874633 to request access.
Go to the SAE Batch Operations page. Select a region and namespace from the top navigation bar.
On the Application Dimension tab, configure the following parameters:
Parameter Value Task Type Application Operation Operation To Perform Change Probe Version Probe Version Number Select the target version Effective Policy See below Select an Effective Policy:
Take Effect On Next Deployment: The new probe version takes effect the next time you manually deploy each selected application. No restart occurs immediately.
Take Effect Immediately: Each selected application is redeployed immediately after you create the task. Perform this during off-peak hours.
Select one or more target applications.
Click Create Task and follow the on-screen instructions.
What's next
Enable Premium monitoring for Standard Edition applications
Learn about ARMS billing