Browser Monitoring alert rules (new version)

Updated at:

Create Browser Monitoring alert rules to configure alerts for your frontend applications. When a rule is triggered, the system notifies specified alert contacts or DingTalk groups, prompting you to take necessary action.

Prerequisites

You have connected your application to Browser Monitoring. For more information, see Browser Monitoring overview.

Procedure

  1. Log on to the ARMS console.

  2. In the left-side navigation pane, choose Browser Monitoring > Browser Monitoring Alert Rules.

  3. On the Browser Monitoring Alert Rules page, click Create Browser Monitoring Alert Rule in the upper-right corner.

  4. On the Create Browser Monitoring Alert Rule page, enter the required information and click Save.

    Note
    • Clicking Save keeps you on the alert rule creation page.

    • Clicking Complete redirects you to the list of alert rules.

    Parameter

    Description

    Alert name

    The name of the alert rule. Example: Page Metric Alert.

    Application

    Select one or more applications for the alert rule.

    Automatically apply this alert rule to newly created applications

    Specifies whether to automatically apply this alert rule to new applications.

    Metric type

    Select the dimension for the monitoring metrics:

    • Custom_Query: Allows you to select metrics from multiple dimensions.

    • Page_API_Metric: Monitors metrics in the page and API dimensions.

    • Custom_Statistics_Metric: Monitors metrics by using a custom statistic key as the dimension.

    • Page_Metric: Monitors metrics in the page dimension.

    • API_Metric: Monitors metrics in the API dimension.

    Note

    The available alert conditions depend on the selected metric type.

    Metric configuration

    • Set filter conditions: The filter expression for the alert rule.

      Note
      • If a filter metric value requires an OR relationship, the expression can use the is one of or is not one of operator, with values separated by a comma (,). For example: api is one of api1,api2,api3.

      • To add multiple filter conditions, click the + icon.

    • Select aggregation dimension: The aggregation dimension is preset based on the metric type. If you set metric type to Custom_Query, you must select an aggregation dimension.

    • Select Metric: When the metric type is multi-dimensional metric, you can select a metric. The metric that you select is used for the metric conditions that you add to an alert rule.

    Alert triggering rules

    • Meet all the following rules: The alert is triggered only when all conditions are met.

    • Meet one of the following rules: The alert is triggered if any condition is met.

    Alert condition

    Click + Add Condition to set up an alert condition expression. For example: The average JS error rate over the last 10 minutes is greater than or equal to 20%. Then, click the 应用监控告警确定图标 icon on the right.

    Note
    • The available conditions depend on the selected aggregation dimension.

    • To modify a condition, click the 应用监控告警修改图标 icon to its right.

    • To preview the metric trend chart for a condition, click the 应用监控告警放大图标 icon to its right.

    • To delete a condition, click the 应用监控告警删除图标 icon to its right.

    • To add multiple alert conditions, click + Add Condition.

    Notification policy

    • Simplified mode: Set the notification recipients, notification period, and repeat policy.

    • Standard mode: Select a notification policy.

      • Do Not Specify Notification Rules: When an alert is triggered, an alert event is generated. A notification is sent only if this event matches a separate notification policy.

      • Specify a notification policy: When an alert is triggered, ARMS sends a notification based on the selected notification policy. You can select an existing notification policy or create a new one. For more information, see Notification policies.

        Note

        Click View to see the details of the selected notification policy.

    Advanced alert settings

    No data

    This setting determines what happens when no data is reported for an alert metric. You can configure the system to treat the value as 0 or 1, or to not trigger an alert.

    For more information, see Alert Management glossary.

Manage alert rules

You can manage your Browser Monitoring alert rules on the Alert rules page. From this page, you can enable, disable, edit, and delete alert rules, and view their alert history.

  1. Log on to the ARMS console.

  2. In the left-side navigation pane, choose Browser Monitoring > Browser Monitoring Alert Rules.

  3. Optional: On the Browser Monitoring Alert Rules page, enter an alert name in the search box and click the search icon.

    Note

    You can perform a fuzzy search by entering a partial alert name.

  4. Find the alert rule and perform one of the following actions in the Actions column:

    • To edit an alert rule, click Edit. On the Edit Alert page, modify the rule and click Save.

    • To delete the alert rule, click Delete, and in the Note dialog box, click Confirm.

    • To start a stopped alert rule, click Start, and in the Note dialog box, click Confirm.

    • To stop a running alert rule, click Stop, and in the Note dialog box, click Confirm.

    • To view the alert history, click Alert History. You are directed to the Alert Event History page.

      Note

      The Alert Event History page lists all events triggered by the alert rule. An event being triggered does not guarantee that a notification is sent; the event must also match a notification policy. To see only the notifications that were sent, go to Alert Management > Alert Sending History in the left-side navigation pane.