Docs

Cloud Monitor

Alert notifications

Receiving NoData alerts via Feishu

In user-side data collection, cloud products may hang, causing resource metrics not to be reported to Cloud Monitor. This topic uses Feishu Webhook as an example to describe how to configure NoData alerts for cloud products. When an alert policy is triggered, alert notifications are pushed to designated Feishu groups. This helps you promptly monitor metrics that have no data.

Considerations

Feishu group bots fall into two types: app bots and custom bots. This topic is about adding a custom bot. For instructions on using Feishu group bots, see How to use bots in groups.

Custom bots are supported only on the Feishu desktop application. Each Feishu group can contain up to 99 bots.

Procedure:

Step 1: Add a bot to a Feishu group

Launch the Feishu desktop app and go to the group where you wish to add a custom bot.

In the upper-right corner of the group chat, select ··· > Settings.

On the Settings page, click Group bot.

In the upper-right corner of Group bot page, click Add bot.

In the Add bot dialog box, find and click Custom bot.

In the pop-up window, set the bot avatar, name, and description, then click Add.

Once the bot is successfully added, you will be able to see its Webhook URL.

tip

To ensure the group bot receives alert notifications, we recommend disabling all the options under Security Settings.

Click Copy next to the Webhook URL to copy the bot Webhook, then click Finish.

Later, when configuring an alert policy in Cloud Monitor, you need to set this bot webhook as the alert callback URL.

Step 2: Create a callback address

In the left navigation bar, click Notification > Callback.

On the Callback address list page, click Create callback address.

On the Create callback address page, complete the following configuration, then click Confirm.

Parameter	Descriptions	Example
Callback address name	Configure a callback address name to identify the callback address. Duplicate names are not allowed.	Feishu NoData alert URL
Callback address type	Select callback address type. Supported types include Feishu, DingTalk, WeCom, and Generic Webhook.	Feishu
Callback address	Enter a publicly accessible URL, then click Test to verify the callback address. If the callback URL returns the HTTP status code 200, it indicates that the connectivity test is successful, and the webhook can receive alerts and event notifications. The connectivity test enforces a one query per second (QPS) limit.	https://open.feishu.cn/open-apis/bot/v2/hook/***

Step 3: Create an alert policy

In the left navigation bar, click Alert center > Alert policy.

On the Alert policy page, click Create Alert policy.

On the Create alert policy page, complete the configuration according to your business needs, then click Confirm.

Parameter description:

Section	Parameter	Descriptions	Example
Basic information	Name	Specify a custom name for the alert policy to identify the alert policy.	NoData alert callback test
Basic information		Description	Specify a custom description for the alert policy.	None
Alert object	resource type	Specify the type of cloud products under monitoring.	Elastic Compute Service (ECS)
		Region	The region of the resources under monitoring.	China (Beijing)
		Subnamespace	Specify the resource dimension of the cloud product under monitoring.	Instance
		Resource	Set the resource scope for the alert policy, meaning monitoring will only be performed within this scope. Available options are as follows: All: Applies the alert policy to all resources under the current account that match the specified resource type, region, and dimensions. After selection, the created resources that meet the conditions will automatically match the alert policy. Part: You need to manually select one or more resources. After selection, the alert policy will be effective only for the selected resources. warning NoData alert notifications will not be sent if the corresponding resource is deleted. For example, when the resource scope of an alert rule is set to "All", deleting a resource (e.g., Resource A) will not trigger a NoData alert, even if the data reports are missing for N consecutive cycles afterward.	All
Alert rules	Metric type	Select the metric type. Available options: Single-metric and Multi-metrics. If you need to monitor multiple metrics of a resource, you can select Multiple-metrics. warning If a rule triggers both a threshold alert and a NoData alert simultaneously, two separate notifications will be sent. Not all cloud service metrics support NoData alerts. At present, NoData alerts can only be configured for cloud product metrics that have an alert rule dimension of "Instance" and involve resources at a single level. Please refer to the console for the actual configuration.	Multiple-metrics
		Trigger condition	Configure the metrics, duration, statistic type, comparison operator, and threshold for the alert. If the monitored resource metric meets the trigger condition, the system will send an alert notification. If the Metric type is set to Single-metric, only one trigger condition can be configured. If the Metric type is set to Multi-metrics, one or more trigger conditions can be configured.	If any metric condition is met for one cycle, an alert is triggered. Average CPU usage > 1% Maximum disk > 10 MiB Average memory usage > 20%
		Alert level	Specify the severity level of the alert. Valid values: Critical, Warning, Notice.	Critical
		Effective time	Configure the effective time of the alert policy. The alert policy monitors resource data against trigger conditions only during its effective time.	00:00~23:59
		Mute For	After an alert policy is triggered, if the monitored resource continuously triggers alerts, the system will periodically send alerts to prevent excessive notifications. Available options include 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, 24 hours. The default value is 5 minutes.	5 minutes
		Alert recovery notification	Send a recovery notification to the user when the alert is resolved. This is enabled by default. warning An alert recovery notification is sent when the alert policy status returns to normal. This indicates that Cloud Monitor has determined the alert has been resolved. In a NoData alert scenario, a recovery notification is sent when the resource resumes data reporting for 5 consecutive minutes.	Enable
		NoData alert	Specify the number of consecutive cycles. A NoData alert will be triggered if no data is reported from the resources of cloud products during those cycles. tip You can configure 3 to 20 cycles. The default value is 10 cycles.	Enable If a resource reports no data for 3 consecutive cycles, a NoData alert will be triggered.
Alert way	Alert channel	Select one or more channels. Valid values: Email, Phone, SMS, and Alert callback.	Alert callback
Alert way		Alert callback	You must specify a public URL as the webhook URL. Later, when a resource triggers the alert policy, the alert details will be sent to this URL via POST for further data analysis. You can select created webhook URLs. Up to eight webhook URLs can be selected. You can enter only one webhook URL. We recommend that you prepare an HTTP server accessible via the Internet, and then set the URL of the server as the callback URL. For more information about alert callback, see Alert callback usage.	Feishu NoData alert URL

Verifying results

View alert notification

Once an alert policy is triggered by a cloud product, the custom bot will send a notification to your Feishu group.

Last updated: 2026.07.15 14:24:29