You can create an alert rule for an application that is monitored by the application monitoring feature. If the alert rule is triggered, Application Real-Time Monitoring Service (ARMS) sends alert notifications to the specified alert contacts or DingTalk groups by using the specified notification methods. This allows you to take necessary measures at the earliest opportunity.

Prerequisites

Your application is connected to ARMS application monitoring. For more information, see Overview.

Procedure

  1. Log on to the ARMS console.
  2. In the left-side navigation pane, choose Application Monitoring > Application Monitoring Alarm rules.
  3. On the page that appears, click Create Application Monitoring Alert Rule in the upper-right corner.
  4. On the page that appears, set the parameters as required and click Save.
    Alert rule for application monitoring
    Parameter Description
    Alert name The name of the alert rule. Example: Period-over-period GCs.
    Alert application The application for which you want to configure the alert rule. You can select multiple applications.
    When you create an application, it is automatically appended to this alert rule Specifies whether to apply this alert rule to a newly monitored application.
    Indicator Type The type of the one or more metrics used in the alert rule. Valid values:
    • JVM_Monitoring
    • Exception_Invocation
    • Invocation_Type
    • Host_Monitoring
    • Invocation_Statistic
    • ThreadPool_Monitoring
    • Database_Metric
    Note The alert conditions and event filter condition that can be configured for the alert rule vary based on the specified metric type.
    Alert trigger rules
    • Specifies how the alert rule is triggered. At the same time meet the following rules: The alert rule is triggered when all alert conditions are met.
    • Meet one of the following rules: The alert rule is triggered when one of the alert conditions is met.
    Alert conditions The alert conditions used to trigger the alert rule. To configure an alert condition, click Add condition. For example, you can use the following alert condition to specify that the alert rule is triggered if the number of full heap garbage collections (GCs) in the last 5 minutes rises by 100% compared with the last hour: Recently5MinutesJVM_Old_GC_Instant_CountAverageUp % year-on-year with last hour 100 %. Then, click the Confirm icon icon on the right.
    Note
    • To edit an alert condition, click the Edit icon icon on the right of the alert condition.
    • To preview the statistics on the metric used in an alert condition, click the Zoom In icon icon on the right of the alert condition.
    • To delete an alert condition, click the Delete icon icon on the right of the alert condition.
    • To configure multiple alert conditions, click Add condition.
    Filter criteria The condition used to filter alert events. Valid values:
    • No: Metric values of all relevant alert events can be shown in the alert notification content.
    • =: Only metric values of the one or more alert events identified by the specified value can be shown in the alert notification content.
    • Traversal: Only metric values of the alert events that trigger the alert rule can be shown in the alert notification content.
    Notification policy
    • The notification policy of the alert rule. If you do not specify a notification policy, no alert notification is sent if the alert rule is triggered. An alert notification is sent only when the dispatch rule of a notification policy is triggered.
    • You can also specify a notification policy. In this case, if the alert rule is triggered, ARMS sends alert notifications based on the notification method specified in the notification policy. You can use an existing notification policy or create a notification policy.
      Note To view the details of the selected notification policy, click View.
    Advanced alert settings
    Alert data revision policy The mode in which to fix anomalies in data, including no data, abnormal composite metrics, and abnormal period-over-period comparisons. If the value of a monitored metric does not meet the specified alert condition, you can use this feature to adjust the value to 0, 1, or null. Valid values:
    • Fill 0: adjusts the value to 0.
    • Fill 1: adjusts the value to 1.
    • Fill Null: does not trigger the alert rule.

Manage alert rules

On the Application Monitoring Alert Rule page, you can enable, disable, edit, and delete an alert rule. You can also view the details of an alert rule.

  1. Log on to the ARMS console.
  2. In the left-side navigation pane, choose Application Monitoring > Application Monitoring Alarm rules.
  3. Optional:On the page that appears, enter an alert rule name in the search box and click the Search icon.
    Note You can enter part of an alert rule name in the search box to perform a fuzzy search.
  4. Perform the following operations on an alert rule based on your business requirements.
    Alert rules for application monitoring
    • To edit an alert rule, click Editing in the Operation column of the alert rule. On the page that appears, edit the alert rule and click Save.
    • To delete an alert rule, click Delete in the Operation column of the alert rule. In the message that appears, click OK.
    • To enable a disabled alert rule, click Start in the Operation column of the alert rule. In the message that appears, click OK.
    • To disable an alert rule that is in effect, click Stop in the Operation column of the alert rule. In the message that appears, click OK.
    • To view the alert event history and notification sending history of an alert rule, click Alarm history in the Operation column of the alert rule. On the page that appears, click the Alert Event History and Alarm Post History tabs to view the history.