Docs

Torch Log Service

Alarm FAQ

Alarm notification channel FAQ

Why is the alarm triggered, but the alarm notification is not received?

After the alarm is triggered, the alarm recipient does not receive the notification. The alarm history page has the alarm event record corresponding to the alarm policy. You can click View Details in its corresponding operation column, and the page will jump to the execution information page of the alarm policy. The notification status column will display Send failed or partially sent successfully .

Possible reason

IAM users have not configured their mobile phone number or email address in their personal information, or have not been verified by their mobile phone number and email address. In the notification group details page, you can find the object that did not receive the alarm notification, and click View in its corresponding receiving channel column. If the object does not pass the security verification, it will be displayed Not configured .

The mobile phone number or email address configured by the IAM user is abnormal and cannot communicate normally.

Triggered the flow control restrictions of some channels in the message center, such as each mobile phone number receiving up to 10 alarm SMS notifications per minute, please refer to the detailed flow control restrictions Limits.

The content of the warning notice is too long.

When using a custom webhook channel and inserting an alert variable in the content template, sending fails if the alert content is parsed in a non-JSON format.

Handling suggestion

Check whether the secure mobile phone and secure mailbox configured by the IAM user have passed the relevant security verification, and the corresponding channels are reached normally.

If a flow control limit is triggered, it is recommended to try again later.

Check the alarm notification content format and content length as expected. Please refer to the format and length description of the notification content of each channel Create content template.

How to set up alarm webhook address access check?

The Log Service Alert Webhook address supports the following access check methods. For more information on alert webhook addresses, please see Create Webhook integration configuration.

Feishu and DingTalk channels

custom keywords

If you configure custom keywords in Feishu or DingTalk robots, you need to add at least one of them to the alarm notification content of the log service. When using this approach, it is recommended to set one of the keywords to alert on the DingTalk or Feishu side.

signature verification

If a signature key is configured in the Feishu or DingTalk bot, it needs to be entered in the Webhook integration configuration on the logging service side.

Other custom webhook addresses

Permission verification through the HTTP request header, that is, add "Authorization": "Bearer ${token}" to the request hea"Authorization": "Bearer ${token}" to the request header , where you need to replace ${token} with your custom Token.

How to turn off alarm recovery notifications?

You can turn off alarm recovery notifications in the notification group configuration.

In the top navigation bar, select the region where the log service is located.

In the left navigation bar, select Common Features > Log Alerts > Notification Management .

On the notification management page, under the notification group page, find the specified notification group and click Edit in its corresponding action Edit in its corresponding action column.

In the Notification Policy on the Edit Notification Policy on the Edit Notification Group page, uncheck Alarm Recovery .

Click Save .

Last updated: 2026.06.25 17:33:46