When front-end issues such as high JS error rates, slow page loads, or failing API calls go undetected, they degrade user experience and impact business outcomes. Application Real-Time Monitoring Service (ARMS) Browser Monitoring alert rules let you define thresholds on these metrics so you receive notifications the moment a threshold is breached.
Prerequisites
Before you begin, make sure that you have:
An application connected to ARMS Browser Monitoring. For more information, see Browser monitoring overview
Create an alert rule
Log on to the ARMS console.
In the left-side navigation pane, choose Browser Monitoring > Browser Monitoring Alert Rules.
Click Create Browser Monitoring Alert Rule in the upper-right corner.
Configure the parameters described in the following sections, then click Save.
Alert name and scope
| Parameter | Description |
|---|---|
| Alert Name | A descriptive name for the rule. Example: Alert for web page-based metric. |
| Select Applications | The Browser Monitoring applications this rule applies to. You can select multiple applications. |
| Automatically apply this alert rule to newly created applications | When enabled, ARMS applies this rule to any application added to Browser Monitoring in the future. |
Metric type
Select the category of metrics to monitor. Your selection determines which alert conditions are available.
| Metric type | When to use | What it monitors |
|---|---|---|
| Page_Metric | Monitor page performance such as load times, DOM parsing, and first paint. | Web page performance metrics |
| API_Metric | Monitor API call health including response times and error rates. | API performance metrics |
| Page_API_Metric | Monitor both page and API metrics in a single rule. | Combined web page and API performance metrics |
| Custom_Statistics_Metric | Monitor custom business metrics you defined in your application code. | Metrics based on custom keys defined in your application |
| Custom_Query | Build a custom alert from specific aggregation dimensions and metrics. Requires manual configuration. | Metrics from custom dimensions |
Filter and aggregate metrics
Configure how ARMS collects and aggregates the data that alert conditions evaluate.
| Parameter | Description |
|---|---|
| Filter Conditions | Narrows the scope of monitored data. For example, API Belong To api1,api2,api3 monitors only the specified APIs. Use Belong To or Not Belong To for OR-based filtering, and separate multiple values with commas. Click the + icon to add more filter expressions. |
| Select Aggregation Dimension | The dimensions used to group metrics. Automatically set for all metric types except Custom_Query, which requires you to select dimensions from the drop-down list. |
| Select Metric | Displayed only when Metric Type is Custom_Query. Select the metrics to use in alert conditions. |
Alert triggering rules
Specify how multiple conditions interact:
Meet all the following rules -- The alert fires only when every condition is met (AND logic).
Meet one of the following rules -- The alert fires when any single condition is met (OR logic).
Alert condition
Define the thresholds that trigger the alert. Each condition specifies a time window, metric, aggregation method, comparator, and threshold value.
Example: Recently 10 Minutes JS_Error_Rate AVG Greater Than or Equal To 20% triggers when the average JS error rate over the past 10 minutes reaches 20% or higher.
To add a condition:
Click + Add Condition.
Select the time window, metric, aggregation method, comparator, and threshold.
Click the confirm icon to save the condition.
After you save a condition, you can:
| Action | How |
|---|---|
| Edit a condition | Click the edit icon next to the condition. |
| View the metric trend chart | Click the more icon next to the condition. |
| Delete a condition | Click the delete icon next to the condition. |
| Add another condition | Click + Add Condition again. |
Tips for effective thresholds:
Start with a wider time window (for example, 10 minutes) and a moderate threshold. Narrow them after you observe real traffic patterns.
Use the metric trend chart (more icon) to review historical data before you set thresholds. This helps you avoid alert fatigue from thresholds that are too sensitive.
For intermittent issues, use Meet all the following rules with multiple conditions to reduce false positives.
Notification policy
Specify how ARMS delivers alert notifications:
Do Not Specify Notification Rules -- ARMS sends notifications only when the alert event matches an event rule in an existing notification policy.
Select or create a notification policy -- Select a policy from the drop-down list, or create a new one. When the alert fires, ARMS sends notifications through the channels configured in the selected policy. Click View to inspect a selected policy.
For more information, see Create and manage a notification policy.
Advanced alert settings
| Parameter | Description |
|---|---|
| No data | Controls how ARMS handles data anomalies such as missing data, abnormal composite metrics, or abnormal period-over-period comparison results. Options include changing the metric value to 0 or 1, or suppressing the alert. For more information, see Terms. |
Manage alert rules
All created alert rules appear on the Browser Monitoring Alert Rules page.
Log on to the ARMS console.
In the left-side navigation pane, choose Browser Monitoring > Browser Monitoring Alert Rules.
*(Optional)* Enter a full or partial alert name in the search box and click the Search icon. Partial names return fuzzy search results.
Locate the target rule and select an action from the Actions column:
| Action | Steps |
|---|---|
| Edit a rule | Click Edit. Modify the parameters on the Edit Alert page, then click Save. |
| Enable a rule | Click Start, then click OK in the confirmation dialog. |
| Disable a rule | Click Stop, then click OK in the confirmation dialog. |
| Delete a rule | Click Delete, then click OK in the confirmation dialog. |
| View alert history | Click Alert History to open the Alert Event History tab and review past alert events. |