EMAS provides an alert management feature that supports anomaly detection and alerting for your pages.
Overview
The alerting feature in Alibaba Cloud EMAS monitors key business metrics in real time. When a metric reaches a preset threshold, the system triggers an alert and sends a notification. You can use the multi-dimensional drill-down analysis to investigate the cause of an alert and respond promptly.
Features
Alert settings
Description: You can set various alert rules as needed. An alert is automatically triggered when a specific metric goes above or below a preset threshold.
Recommendation: Set alerts on key business metrics, such as JS error rate, white screen rate, and page load time, to ensure a prompt response to potential problems.
Multi-dimensional drill-down analysis
Description: After an alert is triggered, you can use the multi-dimensional analysis feature to drill down and identify the specific factors that caused the alert.
Recommendation: Drill down to specific time periods, device types, or regions to quickly identify and locate the root cause of the problem.
Scenarios
Real-time anomaly detection
Scenario description: An Operations and Maintenance (O&M) team sets alert rules to monitor the JS error rate and white screen rate. When the error rate of a page suddenly increases, an alert is immediately triggered and sent to the relevant technical staff.
Key metrics: JS error rate, white screen rate.
Value: Quickly detect anomalies, reduce response time, and minimize user impact.
Performance degradation alerts
Scenario description: A developer team sets a threshold alert for page load time to monitor application performance. An alert is triggered when the page load time exceeds the preset threshold.
Key metrics: Page load time, first screen rendering time.
Value: Promptly detect performance degradation, perform optimizations, and improve the user experience.
Resource consumption control
Scenario description: You can use alerts to monitor the load time and request failure rate of static resources to ensure they load correctly. An alert is triggered when the resource load time is too long or the request failure rate increases.
Key metrics: Resource load time, request failure rate.
Value: Maintain resource loading efficiency and ensure the application runs smoothly.
Use the alert management feature
1. Create an alert contact
Log on to the EMAS Management Console, select Application Monitoring, and click Enter to open the Application Monitoring console.
In the navigation pane on the left, select Alert Management to open the Alert Management page.
On the Alert Management page, click Alert Settings in the upper-right corner and select the Contact Management tab.
Click Add Contact to open the Add Contact page.
Enter the Contact Name, Phone Number, Email, and DingTalk robot webhook address, then click OK.
NoteTo obtain the DingTalk robot webhook address, see How to configure a DingTalk robot for alerts.
2. Create a contact group
On the Alert Settings page, select the Contact Group Management tab.
Click New Group to open the Add Contact Group page.
Enter a Contact Group Name, select the contacts you created, and click OK.
3. Add an alert rule
Log on to the EMAS Management Console, select Application Monitoring, and click Enter to open the Application Monitoring console.
In the navigation pane on the left, select Alert Management to open the Alert Management page.
On the Alert Management page, click Alert Settings in the upper-right corner and select the Alert Rule tab.
On the Alert Rule tab, click Add Rule.
On the Add Alert Rule page, set the following parameters and click OK.
Parameter
Description
Alert Name
Enter a name for the alert.
Problem Type
Select the metric item for which to configure an alert.
Alert Level
Options are Critical or Warning.
Scope
Select the corresponding scope based on the selected Problem Type.
Supported filter conditions: App Version, Device ID, OS Version, Brand, Model, User Nickname, Client IP, Channel, Language, Page, Start Time, Trigger Time, Is Main Thread, Country, Province, City, Resolution, Process, ISP, CPU Architecture, Aggregation ID.
Trigger Condition
You can choose one of two options:
All of the following conditions are met.
Any of the following conditions is met.
Note
You can add multiple metric policies.
Last N minutes: The size of the time window for checking data.
Metric: Different problem types have different metrics.
Filter conditions:
Threshold: An alert is triggered if the number of anomalies in a single time window reaches a certain amount.
Ratio: An alert is triggered if the value in a single time window increases or decreases by more than the set value compared to the same time window n time units ago.
Allowed Notification Period
Set the notification period and interval.
Alert Channel
Select the method for sending alerts. Options include email, text message, and DingTalk.
Note
The alert contact must have the corresponding contact method configured to receive alerts.
Contact Group
Select a configured contact group.
To deactivate a rule that is not currently needed, go to the Alert Rule tab and click Disable in the Actions column.
4. View alerts
Log on to the EMAS Management Console, select Application Monitoring, and click Enter to open the Application Monitoring console.
In the navigation pane on the left, select Alert Management to open the Alert Management page.
You can also search for alerts by Time, Problem Type, Alert Level, or Rule Name.
Click Analyze and Process next to an alert to open the drill-down data page.
NoteOn the alert analysis and processing page, you can change the bug status to New, Open, or Fixed.
FAQ
How to configure a DingTalk robot for alerts
Add a DingTalk robot to a DingTalk group and obtain the webhook address.
Select the target DingTalk group, and in the upper-right corner, click Group Settings > Robot > Add Robot > Custom > Add.
ImportantIn the Security Settings on the Add Robot page, you must select the Custom Keywords option and add "EMAS" as a keyword.
After the item is added, a Webhook URL is generated. The following is an example:
https://oapi.dingtalk.com/robot/send?access_token=XXXXXXIn the contact settings of the Application Monitoring console, configure the webhook address for the DingTalk robot. For more information, see Create an alert contact.