This topic describes how to create an alert rule for monitoring an application in Enterprise Distributed Application Service (EDAS). This topic also describes how to manage alert rules. When an alert rule is triggered, EDAS sends an alert notification over the notification method that you specified. You can send notifications to contacts or DingTalk groups. Notifications help remind the relevant persons to resolve issues at their earliest opportunity.

Prerequisites

Your application is added to Application Monitoring. For more information, see Overview.

Procedure

  1. Log on to the EDAS console.
  2. On the Applications page, select EDAS Kubernetes Cluster or Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, click the name of the application for which you want to create an alert rule.
  3. In the left-side navigation pane, choose Alert Management > Alert Rule.
  4. On the Alert Rule page, click Create Application Monitoring Alert Rule in the upper-right corner.
  5. On the Create Application Monitoring Alert Rule page, set the required parameters and click Save.
    Create Application Monitoring Alert Rule
    Parameter Description
    Alert Name The name of the alert. For example, you can enter "Alert on JVM-GC times in period-over-period comparison."
    Alert Application The application to which the alert rule applies.
    Indicator Type The type of the monitoring metric. Valid values:
    • JVM_Monitoring
    • Exception_Invocation
    • Invocation_Type
    • Host_Monitoring
    • Invocation_Statistic
    • ThreadPool_Monitoring
    • Database_Metric
    Note The values of the Alert Conditions and Filter criteria parameters vary with that of the Indicator Type parameter.
    Alert Triggering Rules
    • At the same time meet the following rules: The alert is generated only when all the conditions are met.
    • Meet one of the following rules: The alert is generated when one of the conditions is met.
    Alert Conditions The conditions for generating an alert. You can click Add condition to create an alert condition. For example, you can specify that an alert is generated when the five-minute average of JVM_FullGC has a 100% hour-on-hour increase. After you set an alert condition, click the Confirm icon icon to save the condition.
    Note
    • To modify an alert condition, click the Edit icon icon next to the alert condition.
    • To view the trend chart of the metric in an alert condition, click the More icon icon next to the alert condition.
    • To delete an alert condition, click the Delete icon icon next to the alert condition.
    • If you want to set multiple alert conditions, click Add condition to create another condition.
    Filter criteria The scope of monitoring metrics that are checked. Valid values:
    • None: The sum of all metric values determines whether an alert is generated.
    • =: You can specify one or more values for this parameter to set a scope of monitoring metrics. The system identifies the metric values that trigger the alert condition in this scope.
    • Traversal: When you set the parameter to this value, the system performs a traversal task to check the metric value one by one, and then identifies all metric values that trigger the alert condition.
    Notification Policy
    • Do not specify a notification rule: An alert notification is sent only when the dispatch rule in the notification policy is triggered.
    • Specify a notification rule: When an alert is generated, ARMS sends alert notifications by using the notification method that is specified in the notification policy. You can select an existing notification policy from the drop-down list, or create a notification policy. For more information, see Notification policies.
      Note You can click View to view the details of the selected notification policy.
    Advanced Alert Settings
    Alert Data Revision Policy This parameter is used to fix data anomalies, such as no data, abnormal composite metrics, and abnormal period-over-period comparison results. When a data anomaly occurs, the alert condition cannot be met. You can set this parameter to Fill 0, Fill 1, or Fill Null to ensure accurate monitoring results.
    • Fill 0: sets the abnormal metric value to 0.
    • Fill 1: sets the abnormal metric value to 1.
    • Fill Null: does not trigger the alert condition.

    For more information, see Terms.

Manage alert rules

The Alert Rule page displays all created alert rules. You can enable, disable, modify, or delete the alert rules, or view the details of an alert rule on this page.

  1. Log on to the EDAS console.
  2. On the Applications page, select EDAS Kubernetes Cluster or Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, click the name of the application for which you want to manage alert rules.
  3. In the left-side navigation pane, choose Alert Management > Alert Rule.
  4. Optional:On the Alert Rule page, enter the alert name in the search box and click the Search icon.
    Note You can enter part of an alert name in the search box to perform a fuzzy search.
  5. Find the alert rule that you want to manage and perform the following operations in the Actions column based on your business requirements:
    Alert Rule
    • To modify an alert rule, click Edit. On the Edit alerts page, modify the alert rule and click Save.
    • To delete an alert rule, click Delete. In the Cue message, click OK.
    • To enable an alert rule, click Start. In the Cue message, click OK.
    • To disable an alert rule, click Stop. In the Cue message, click OK.
    • To view historical alert events or alert sending records, click Alert history. On the page that appears, click Alert Event History or Alert Sending History in the left-side navigation pane to view corresponding records.