This topic describes the terms related to alert management in Enterprise Distributed Application Service (EDAS).
B
- Set 0, Set 1, and Set Null
-
You can set the Alarm Data Revision parameter when you create an alert. Valid values of the Alarm Data Revision parameter include Set 0, Set 1, and Set Null (Won't Trigger). The default value is Set Null (Won't Trigger). In most cases, this parameter is used to fix data anomalies, including no data, abnormal compound indicators, and abnormal period-over-period comparisons.
- Set 0: fixes the checked value to 0.
- Set 1: fixes the checked value to 1.
- Set Null (Won't Trigger): does not trigger an alert.
Scenarios:- Anomaly 1: no data
User A wants to use the alert feature to monitor page views. When User A creates an alert, User A selects Browser Monitoring Alarm. User A sets the following alert rule: N is 5, and the sum of page views is not greater than 10. If the page is not accessed, no data is reported, and no alert is sent. To resolve this issue, User A can select Set 0 for the Alarm Data Revision parameter. If no data is received, the system determines that zero data records are received. This meets the conditions specified in the alert rule. Therefore, an alert is sent.
- Anomaly 2: abnormal compound indicators
User B wants to use the alert feature to monitor the real-time unit price of a commodity. When User B creates an alert, User B selects Custom Monitoring Alarm. User B sets the dataset of variable a to the current total price, and the dataset of variable b to the current total number of items. User B also sets an alert rule. In this rule, N is 3, and the minimum value of the current total price divided by the current total number of items is less than or equal to 10. If the current total number of items is 0, the value of the compound indicator (the current total price divided by the current total number of items) does not exist. No alert is sent. To resolve this issue, User B can select Set 0 for the Alarm Data Revision parameter. If the value of the compound indicator (the current total price divided by the current total number of items) does not exist, the system determines that the value is 0. This meets the conditions specified in the alert rule. Therefore, an alert is sent.
- Anomaly 3: abnormal period-over-period comparisons
User C wants to use the alert feature to monitor the CPU utilization of a node. When User C creates an alert, User C selects Application Monitoring Alarm. User C also sets the following alert rule: N is 3, and the average CPU utilization of the node decreases by 100% compared with that in the previous monitoring period. If the CPU of the user fails in the last N minutes, the system cannot obtain α. This means that the period-over-period comparison result does not exist. No alert is sent. To resolve this issue, User C can select Set 1 for the Alarm Data Revision parameter. If α is not obtained, the system determines that the period-over-period comparison result is a decrease of 100%. This meets the conditions specified in the alert rule. Therefore, an alert is sent.
C
- re-trigger escalation rules
- If an alert remains unresolved after all escalation rules in an escalation policy are triggered, the system re-triggers the escalation rules. By default, the escalation rules are re-triggered only once. You can configure the system to re-trigger the escalation rules for up to nine times.
G
- alert
- Alerts are events that must be resolved by contacts. When events are triggered by notification policies, if the events must be resolved, the system generates and sends alerts to alert contacts.
- alert management
- The feature to manage alerts.
- alert card
- The chatbot of DingTalk groups sends alert notifications to DingTalk groups in the form of alert cards. Alert contacts in the DingTalk groups can use the alert cards to view, handle, and resolve alerts. You can configure the chatbot on the DingTalk Group tab of the Contact page in the EDAS console.
- automatic change of the alert status
- When alerts are resolved, the system automatically changes the status of the alerts to resolved.
- anomaly
- Business rules may cause abnormal monitoring data. After monitoring services detect abnormal monitoring data, the system generates the corresponding events.
H
- minute-on-minute comparison
- Assume that β is the data (optionally average value, sum, maximum value, or minimum value) in the last N minutes, and α is the data generated between the last 2N and N minutes. You can obtain the percentage that is increased or decreased by comparing β with α.
L
- contact
- Contacts refer to O&M engineers who handle alerts. Contacts can view, handle, and resolve alerts in DingTalk.
R
- claim to handle alerts
- If contacts want to handle unresolved alerts, they can claim to handle the alerts.
S
- timeout of alert escalation
- When an alert escalation times out, the system sends notifications of unresolved or unconfirmed alerts to the contacts who are specified in the escalation policy. The default timeout period for an alert escalation is 10 minutes. The maximum timeout period is 90 minutes.
- escalation policy
- When an alert escalation times out, the system sends alert notifications in sequence to different batches of contacts who are specified in the escalation rules. You can add an escalation policy to a notification policy.
- group events
- You can group multiple events into a single alert to prevent notification bombing. This also helps to summarize the keywords of notifications so that the contacts can get quick understandings of the situation.
- silence events
- You can silence unimportant events. Notifications are not sent for the silenced events.
- automatic recovery of events
- Events can be automatically recovered after a specified period of time. After this period of time, the events are automatically counted as resolved ones. By default, events are automatically recovered after 5 minutes.
T
- minute-on-minute hourly comparison
- Assume that β is the data (optionally average value, sum, maximum value, or minimum value) in the last N minutes, and α is the data generated during the last N minutes in the previous hour. You can obtain the percentage that is increased or decreased by comparing β with α.
- minute-on-minute daily comparison
- Assume that β is the data (optionally average value, sum, maximum value, or minimum value) in the last N minutes, and α is the data generated during the last N minutes at the same time yesterday. You can obtain the percentage that is increased or decreased by comparing β with α.
- alert notification
- When alerts are triggered, the system immediately sends alert notifications to alert contacts. Notifications describe the objects that trigger the alerts and have a title. Notifications can be sent in forms of text messages, emails, WeChat messages, alert cards in DingTalk groups, and WebHooks.
- notification policy
- A notification policy determines how to group events into a single alert and send alert notifications to alert contacts. You can send notifications in forms of phone calls, text messages, emails, or alert cards in DingTalk groups. Notifications are sent to contacts in 1 minute after the corresponding notification policies are triggered.
Y
- user
- Users refer to Alibaba Cloud accounts and RAM users. Users can perform the following
operations in the EDAS console:
- Create and modify notification policies.
- Create and modify escalation policies.
- View, handle, and resolve alerts.