If you have created an alert rule but have not received an alert notification, perform the troubleshooting described in this topic.
Troubleshooting
Check whether a threshold-triggered alert rule is triggered with a delay.
For more information about the cause, see Why is a threshold-triggered alert rule triggered with a delay?.
On the Alert History page, filter the historical alerts by rule name, cloud service, and alert trigger time to check whether alerts are triggered.
For more information about how to view the alert history, see View historical alerts.
If no historical alert is found, no metric meets the alert conditions and no alert notification is sent. For more information about how to troubleshoot the issue, see What do I do if no alert is triggered when the corresponding metric value meets the specified alert condition?
If alerts are found, view the Status column in the Alert History section.
In most cases, alert notifications are sent if Alerts and Back to normal are displayed in the Status column. However, no alert notification is sent in the following two special cases:
If Hit blacklist is also displayed in the Status column, an alert blacklist is configured for the instance and no alert notification is sent.
For Container Service for Kubernetes (ACK) alerts, a mute period is specified for alerts by alert level based on an alert rule. If alerts are triggered for multiple instances during the mute period, only one alert notification is sent.
If the following values are displayed in the Status column, it is expected that no alert notification is sent. The following list describes the alert states:
Not in the effective period: The alert is not triggered within the effective period configured for the alert rule.
Mute Period: An alert is triggered during the mute period and is not cleared.
Do not send: The alert rule specifies that no alert notification is sent when an alert is cleared.
Check whether the alert contacts and alert notification methods are correct.
On the Alert Contact Group tab of the Alert Contacts page, find the alert contact group configured in the alert rule and click the
icon to check whether the alert contact group is scheduled. If the alert contact group is scheduled, confirm the specific alert contacts and their shifts based on the schedule.
If the alert contact group is not scheduled, click the alert contact group to view the alert contacts and their notification addresses.
After you confirm the alert contacts, alert notifications may not be sent for all alert notification methods.
Alerts of different levels have different alert notification methods. For example, if an Info-level alert is triggered, the alert contacts receive no alert text message or alert phone call. The following items list the alert notification methods for alerts of different levels.
Critical: email, webhook, and alert callback
Warn: email, webhook, and alert callback
Info: email, webhook, and alert callback
If the alert notification address of an alert contact does not receive an alert notification as expected, check the alert notification details.
On the Alert History page, click the alert contact group in the Notification Contacts column of the alert history.
On the Notification Contacts tab, the notification methods of all alert contacts in the alert contact group are displayed.
Move the pointer over the alert notification result icon to view the notification details returned for each alert notification method.
Solution
If you still do not receive an alert notification after you perform the preceding troubleshooting and find no issue, check the following possible causes and solutions for different alert notification methods:
Email
The number of alert notifications that are sent per day exceeds the limit. No more alert notifications are sent. An email address can receive up to 1,000 emails per day.
Webhook
Query the error code in the documentation of the related communication software or submit a ticket to the communication software based on the error code in the notification details of the Notification Contacts column in the Alert History section.
For example, the failure details in a DingTalk notification is
{"messageType":"DING","httpResponse":"{\"errcode\":90030,\"errmsg\":\"webhook over limit\"}","httpStatusCode":200}. You can search for the DingTalk documentation to find that the cause of the failure is free commercialization of webhooks.Alert callback
Determine the cause based on the error code in the notification details of the Notification Contacts column in the Alert History section. The possible causes include security interception and invalid parameter formats. For more information about how to troubleshoot the issue, see What do I do if I cannot receive alert notifications by using an alert callback?