You can create application monitoring alert rules for specific metrics of application monitoring. When an alert rule is triggered, the system sends an alert notification to the specified contact or DingTalk group by using the specified notification method. This reminds you to take necessary measures to resolve the issue.

Prerequisites

An Enterprise Distributed Application Service (EDAS) application is connected to Application Real-Time Monitoring Service (ARMS). 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 that you want to manage.
  3. In the left-side navigation pane, choose Alert Management > Alert Rules.
  4. On the Application Monitoring 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 parameters and click Save.
    Parameter Description
    Alert name The name of the alert. Example: JVM-GC_Comparison.
    Alert application The application for which you want to create the alert rule. You can select one or more applications.
    When you create an application, it is automatically appended to this alert rule Specifies whether to automatically apply this alert rule to new applications.
    Indicator Type The type of metric that you want to monitor. Valid values:
    • JVM_Monitoring
    • Exception_Invocation
    • Invocation_Type
    • Host_Monitoring
    • Invocation_Statistic
    • ThreadPool_Monitoring
    • Database_Metric
    Note The fields of the trigger condition and the filter condition vary with the metric type.
    Alert trigger rules
    • At the same time meet the following rules
    • Meet one of the following rules
    Alert conditions Click Add condition to configure a trigger condition. For example, enter 5 in the Recently field, and select JVM_Old_GC_Instant_Count, AVG, Up% from last hour, and 100% from the drop-down lists. This condition is met when the average number of full heap garbage collections (Full GCs) in the last 5 minutes increases by at least 100% compared with that in the previous hour. Then, click the OK icon for a trigger condition icon to the right of the trigger condition.
    Note
    • You can click the Modify icon for a trigger condition icon to the right of a trigger condition to modify the trigger condition.
    • You can click the Zoom in icon for a trigger condition icon to the right of a trigger condition to preview the trend chart of the related metric when the trigger condition is applied.
    • You can click the Delete icon for a trigger condition icon to the right of a trigger condition to delete the trigger condition.
    • To configure multiple trigger conditions, click Add condition to configure the second trigger condition.
    Filter criteria The dimension of the metric. Valid values:
    • No: The alert content shows the sum of all the values of this dimension.
    • =: The alert content shows only the specified value of this dimension.
    • Traversal: The alert content shows the dimension content that triggers the alert rule.
    Notification policy
    • Do not specify a notification rule: An alert notification is not sent when the alert rule is triggered. An alert notification is sent only when the dispatch rule in the notification policy is triggered.
    • Specify notification rules to send alerts: When the alert rule is triggered, EDAS sends an alert notification by using the notification method in the specified notification policy. You can select an existing notification policy or create a notification policy. For more information, see Configure a notification policy.
      Note Click See to view the details of the selected notification policy.
    Advanced alert settings
    Alert data revision policy The method for fixing data anomalies, including no data, abnormal compound indicators, and abnormal period-over-period comparisons. If the value of the metric does not meet the specified condition, the value is fixed to 0 or 1, or the alert rule is not triggered.
    • Zero fill: fixes the checked value to 0.
    • One fill: fixes the checked value to 1.
    • Null file: does not trigger the alert rule.

    For more information, see Terms.

Manage alert rules

Created application monitoring alert rules are displayed on the Application Monitoring Alert Rule page. You can manage the alert rules. For example, you can enable, disable, modify, and delete the alert rules, and view the details of the alert rules.

  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 that you want to manage.
  3. In the left-side navigation pane, choose Alert Management > Alert Rules.
  4. Optional:On the Application Monitoring Alert Rule page, enter an alert name in the search box and click the search icon.
    Note You can enter a part of an alert name in the search bar to perform a fuzzy search.
  5. In the Operation column of the search result list, perform the following operations as needed to manage an alert rule:
    List of application monitoring alert rules
    • To modify an alert rule, click Editing in the Operation column. On the Edit alerts page, modify the alert rule and click Save.
    • To delete an alert rule, click Delete in the Operation column. In the Cue message, click OK.
    • To enable a disabled alert rule, click Start in the Operation column. In the Cue message, click OK.
    • To disable an enabled alert rule, click Stop in the Operation column. In the Cue message, click OK.
    • To view the alert events and alert notification records for an alert rule, click Alarm history in the Operation column. On the Event List and Alarm pages, view the alert events and alert notification records for the alert rule.