All Products
Search
Document Center

Enterprise Distributed Application Service:Create application monitoring alert rules and handle notifications

Last Updated:Oct 24, 2026

This topic describes how to create an alert rule for application monitoring and handle alert notifications.

Prerequisites

Your application is connected to application monitoring. For more information, see Application monitoring overview.

Background information

EDAS application monitoring allows you to configure alert rules for various application metrics. You can define alert rules based on your business requirements to receive timely notifications when an application underperforms, allowing you to respond quickly. This topic uses the following scenario to demonstrate how to use EDAS application monitoring alert rules.

Example scenario: The response time of a core business service is too high, or its request success rate drops.

Example application: user-service. The user-service application is a Java application deployed in an Alibaba Cloud Container Service for Kubernetes (ACK) cluster. The application is connected to EDAS application monitoring.

The user-service application runs a critical service. A decrease in the availability of its APIs can have serious consequences. Therefore, operations engineers must receive timely notifications and respond quickly when the API response time increases or the request success rate drops.

In this scenario, operations engineers need to monitor the following metrics:

  • Average response time of the services provided by the application

  • Request success rate of the services provided by the application

Step 1: Verify the application connection

Verify that the user-service application is connected to application monitoring.

  1. Log on to the EDAS console.

  2. In the left-side navigation pane, choose Application Management > Applications, find and click the name of the user-service application.

    1. In the left-side navigation pane, click Application Overview.

    2. Go to the Application Overview page and check if the Application Overview page contains data.

    If data is displayed, the application is connected. If no data is displayed, the connection failed. You must reconnect the application to application monitoring.

    Note

    The example application is a Java application that runs in a Container Service for Kubernetes (ACK) cluster. If your application is of a different type, the page may look different after a successful connection. However, the connection is successful as long as metric data is displayed.

Step 2: Go to the create alert rule page

  1. Log on to the EDAS console.

  2. In the left-side navigation pane, click Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy and click the application name.

  3. In the left-side navigation pane, choose Alert Management > Alert Rule.

  4. In the upper-right corner of the Alert Rule page, click Create Application Monitoring Alert Rule.

  5. On the Create Application Monitoring Alert Rule page, set alert application to user-service and metric type to Application Invocation Type Statistics.

Step 3: Create alert rules

In this example, two alert rules are created. When an alert is triggered, notifications are sent to the specified contacts by SMS, email, and DingTalk group.

  • Alert rule for high request latency for the user-service application:

    Average response time for service calls is greater than or equal to 500 ms for the last 3 minutes.
  • Alert rule for a drop in request success rate for the user-service application:

    Request success rate for service calls is less than or equal to 90% for the last 3 minutes.
Note

Short-term fluctuations in API performance are generally considered normal. However, sustained anomalies require attention. Therefore, you can configure an alert rule to trigger only when a metric remains anomalous for a specified period, such as 3 minutes. You can specify different time periods and metric calculation methods when you create your alert rules.

  1. On the Create Application Monitoring Alert Rule page, enter a name for the alert rule and add an alert condition.

    First, create the alert condition for the high request latency of the user-service application.

  2. Set a notification policy.

    • If you have already created a notification policy, select it in the notification policy section.

    • If you have not created a notification policy, create one by following Step 3 of this section. After the policy is created, refresh the Create Application Monitoring Alert Rule page and select the new notification policy.

  3. Optional: Click Create Notification Policy next to notification policy.

    In the Create Notification Policy panel that appears on the right, select a contact, configure the other parameters, and then click OK.

    • If you have already created a contact, select the contact in the contact section.

    • If you have not created a contact, create one by following Step 4 of this section. After the contact is created, refresh the Create Notification Policy panel and select the new contact.

    新建通知策略

  4. Optional: Click Create Contact next to contact.

    On the Contacts page, you can create contacts, contact groups, and DingTalk groups.

    1. On the Contacts tab, click Create Contact in the upper-right corner.

    2. In the Create Contact dialog box, enter the contact parameters and click OK.

    3. On the Contact Groups tab, click Create Contact Group in the upper-right corner.

    4. In the Create Contact Group dialog box, enter a group name, add the contact that you just created to the contact group, and then click OK.

      After the contact group is created, you can view it on the Contact Groups tab.

    5. On the DingTalk Group tab, click Create DingTalk Group in the upper-right corner.

    6. In the Create DingTalk Group dialog box, configure the parameters for the DingTalk group and click OK.

      After the DingTalk group is created, you can view it on the DingTalk Group tab.新建钉群

  5. After you configure the alert rule, click Save.

  6. Repeat the preceding steps to create the alert rule for a drop in the request success rate for the user-service application.

    After the alert rules are created, you can view them on the Alert Management > Alert Rule page in the console.

Handle alerts

After receiving a notification, go to the alert management page to view the alert history and detailed event information.

  1. Log on to the EDAS console.

  2. In the left-side navigation pane, click Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy and click the application name.

  3. In the left-side navigation pane, choose Alert Management > Alert History.

    On the Alerts page, you can view the alert history with detailed time information. For more information, see View alert history.