Help Center/ Cloud Eye/ User Guide/ Alarm Management/ Alarm Notifications/ Creating a Recipient/Notification Group
Updated on 2026-06-18 GMT+08:00

Creating a Recipient/Notification Group

A recipient receives notifications. Cloud Eye notifies them by SMS, email, voice notification, HTTP, HTTPS, FunctionGraph (function), FunctionGraph (workflow), WeCom, DingTalk, Lark, or WeLink. You can create recipients and choose desired notification channels.

A notification group consists of one or more recipients and can contain one or more notification channels. You need to create recipients and a notification group, and add the recipients to the notification group. When creating an alarm rule, you can select this group for receiving alarm notifications. The alarm notifications are automatically sent to all its members.

In some regions, recipients are now called contacts, and notification groups are now contact groups. For details, see the console.

Billing

Alarm notifications sent by SMN will be billed based on their frequency and message length. For details, see Product Pricing Details.

Constraints

  • If the notification channel for a recipient is set to Email, SMS, or Voice Notification, the email address or mobile number cannot exceed 300 characters. Otherwise, the recipient may fail to be added to a notification group.
  • You can add up to 10 recipients to a notification group.

Creating a recipient

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Notifications.
  2. Click the Recipients tab, click Create, and configure parameters.
    Figure 1 Creating a recipient

    Table 1 Parameters for creating a recipient

    Parameter

    Description

    Recipient Name

    Name of a recipient. Enter 1 to 42 characters.

    Protocol

    Over which protocol alarm notifications will be sent. Only one object can be added for each protocol.

    • Email: Enter a valid email address.

      Example: username@example.com

    • WeCom: Enter the webhook URL for receiving alarm notifications. Locate a WeCom group chatbot and click New in the upper right corner. After the chatbot is added, obtain its webhook URL.

      Example: https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=your_key

    • HTTP: Enter a valid public network URL.

      Example: http://example.com

    • HTTPS: Enter a valid public network URL.

      Example: https://example.com

    • FunctionGraph (function): Select a function and version.
    • FunctionGraph (workflow): Select a workflow.
    • DingTalk: Enter the webhook URL for receiving notifications and determine whether to configure security settings. Open DingTalk, go to a DingTalk group and click the Group Settings icon in the upper right corner. When you add a chatbot, select Custom. After the chatbot is created, obtain its webhook URL.

      Example: https://oapi.dingtalk.com/robot/send?access_token=XXXXXX

    • Lark: Enter the webhook URL and configure security settings. Open Lark on a PC. Locate a group chat. In the group settings, choose BOTS, click Add Bot, and select Custom Bot. After the chatbot is added, obtain its webhook URL, for example, https://open.feishu.cn/open-apis/bot/v2/hook/xxx. Obtain the key in Security Settings of the Lark chatbot.
    • WeLink: Enter the group ID and configure security settings for receiving notifications. Obtain client_id and client_secret from Basic Information of an internal enterprise app on the developer backend of WeLink Open Platform.
    NOTE:
    If you select SMS, Email, HTTP, HTTPS, or Voice Notification, SMN will send subscription confirmation messages to the subscription endpoints. The subscriber can receive alarm notifications only after confirming the subscription. For other channels, subscription confirmation is not required.
    • If you select SMS, Email, HTTP, or HTTPS, SMN will send subscription confirmation messages to the subscription endpoints after the recipient is created. The recipient can be bound to a notification group only after subscription confirmation. Subscription confirmation is not required again during such binding. If a recipient that has been added but not modified is added to a notification group, SMN will send subscription confirmation messages to the subscription endpoints. In some regions, SMN will send subscription confirmation messages when a recipient is added to a notification group.
    • If you select Voice Notification, SMN will send a subscription confirmation message to the subscription endpoint after the recipient is added to a notification group.
  3. Click Create.

Creating a Notification Group

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Notifications.
  2. Click the Notification Groups tab, click Create, and configure parameters.
    Figure 2 Creating a notification group

    Table 2 Parameters for creating a notification group

    Parameter

    Description

    Group

    Name of the notification group. Use only letters, digits, underscores (_), and hyphens (-). Enter up to 64 characters.

    Enterprise Project

    Enterprise project that the notification group belongs to. Only users who have all permissions for the enterprise project can manage this group. For details about how to create an enterprise project, see Creating an Enterprise Project.

    Recipient

    Recipients for receiving notifications.

  3. Click Create.

Adding Recipients to a Notification Group

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Notifications.
  2. Click the Notification Groups tab, locate the row that contains the target notification group, and click Add Recipient in the Operation column.
  3. In the displayed drawer, select the recipients you want to add and click OK.
    Figure 3 Adding a recipient

Helpful Links

  • If recipients do not receive subscription or notification messages after the configuration is complete, rectify the fault by referring to Why Do Subscribers Fail to Receive Messages After I Publish Messages to a Topic?
  • Sending excessive messages can lower the SMN service quality for everyone. The cloud platform limits how often endpoints receive notifications to avoid this issue. When notification limits are exceeded, SMN will stop sending new notifications. For details about the limits, see Resilience.