Terms - Application Real-Time Monitoring Service - Alibaba Cloud Documentation Center

B | C | G | H | J | L | R | S | T | Y

B

Fill 0, Fill 1, or Fill Null

When you create an alert rule, you can set the Alert Data Revision Policy parameter to Fill 0, Fill 1, or Fill Null. This feature allows you to fix data anomalies, such as no data, abnormal composite metrics, and abnormal period-over-period comparisons.

Fill 0: fixes the checked value to 0.
Fill 1: fixes the checked value to 1.
Fill Null: does not trigger an alert.

Scenarios:

Anomaly 1: no data
User A wants to use the alerting feature to monitor page views. When User A creates an alert rule in Browser Monitoring, User A specifies that an alert is triggered when N is 5, and the sum of page views is less than or equal to 10. If the page is not accessed, no data is reported, and no alert notification is sent. To resolve this issue, User A can select Fill 0 for the Alarm Data Revision Policy parameter. If no data is received, the system determines that zero data records are received. This meets the conditions specified in the alert rule, and an alert notification is sent.
Anomaly 2: abnormal composite metrics
User B wants to use the alerting feature to monitor the real-time unit price of a commodity. When User B creates an alert rule in ARMS, User B sets the dataset of variable a to the current total fee, and the dataset of variable b to the current total number of items. User B specifies that an alert is triggered when N is 3, and the minimum value of the current total fee 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 composite metric, which is the current total price divided by the current total number of items, does not exist. No alert notification is sent. To resolve this issue, User B can select Fill 0 for the Alarm Data Revision Policy parameter. This way, if the value of the composite metric does not exist, the system determines that the value is 0. This meets the conditions specified in the alert rule, and an alert notification is sent.
Anomaly 3: abnormal period-over-period comparisons
User C wants to use the alerting feature to monitor the CPU utilization of a node. When User C creates an alert rule in Application Monitoring, User C specifies that an alert is triggered when 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 fails in the last N minutes, the system cannot obtain α, which is used to calculate the the period-over-period comparison result. In this case, the comparison result does not exist. No alert notification is sent. To resolve this issue, User C can select Fill 1 for the Alarm Data Revision Policy 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, and an alert notification 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.

[Back to Top]

G

alert: Alerts are events that must be resolved by contacts. Alerts are generated only when events meet the conditions specified in notification policies and must be resolved.
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. Contacts can use the alert cards to view, handle, and resolve alerts. You can configure the chatbot on the IM robot tab in the ARMS console.
automatic resolution of alerts: When alerts are resolved, the system automatically changes the status of the alerts to Resolved.
anomaly: Business rules may cause abnormal monitoring data. When abnormal monitoring data is detected, the system generates events.

[Back to Top]

H

comparison with the previous period: If β is the data (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 α.

J

integration: You can integrate most monitoring services with the alert management feature by using APIs.

[Back to Top]

L

contact: Contacts refer to O&M engineers who handle alerts. Contacts can view, handle, and resolve alerts in DingTalk.

[Back to Top]

R

claim alerts: If contacts want to handle unresolved alerts, they can claim the alerts.

[Back to Top]

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 that you can specify 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 policy. You can add an escalation policy to a notification policy.
event: The integrated monitoring services send events to the alert management feature. The system generates an alert for each event unless the event is silenced.
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 a quick understanding of the situation.
silence events: You can silence unimportant events. Alerts are not generated for silenced events.
remove duplicated events: After the integrated monitoring services send events to the alert management feature, the duplicate events are removed, but the number of duplications is recorded.
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.

[Back to Top]

T

comparison with the same period in the previous hour: If β is the data (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 α.
comparison with the same period in the previous day: If β is the data (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 in the previous day, you can obtain the percentage that is increased or decreased by comparing β with α.
notification: When alerts are triggered, the system immediately sends alert notifications to alert contacts. Notifications contain information about the objects that trigger the alerts and have a title. Notifications can be sent in the form of text messages, emails, WeChat messages, alert cards in DingTalk groups, and webhook messages.
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 the form 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.