> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Alert Notification Targets

> Create and manage alert notification targets, contact groups, and third-party applications in Siverse to receive messages sent by alert subscriptions.

Notification management is used to manage alert recipients. Before creating an alert subscription, you must first prepare available notification targets.

## Notification Recipient Relationships

| Object | Description | Usage |
| - | - | - |
| Notification targets | The smallest alert delivery unit. It defines a notification method and a recipient address or recipient. | Can be directly associated with an alert subscription. |
| Contact groups | A collection of multiple notification targets. | Can be associated with an alert subscription as a whole. |
| Third-party applications | Enterprise application configuration, such as for Feishu applications. | Referenced by Feishu application message notification targets. |

Both notification targets and contact groups can be enabled or disabled. If disabled, alert delivery that depends on the object may be affected.

## Create a Notification Target

### 1. Go to the Creation Page

1. Go to **Alarm > Notification Management**.
2. On the **Notify Targets** tab, click **Create**.

### 2. Configure Notification Methods

Select a **Method** and complete the configuration on the corresponding tab.

![Alert notification target configuration](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/alerts/media/alert-notification-target-form.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=2098be5258de320d5cc0753025c539d8)

**Feishu Notice**

**Feishu Notifications** are suitable for sending alerts to specified Feishu users.

| Configuration Item | Description |
| - | - |
| **Third-Party Application** | Select an available Feishu application. If no Feishu applications are available in the tenant, regular users cannot create Feishu notifications. |
| **Phone Number Bound to Feishu** | Enter the recipient's phone number bound to Feishu. |
| **Remark** | Describe the purpose of the notification target to facilitate subsequent maintenance. |
| **Language** | Select the display language for alert messages. |
| **Visible Scope** | **Only Self** means that only the creator can use it; **Public** means that it can be reused within the same tenant. |
| **Enabled** | Controls whether this notification target participates in alert delivery. |

**Webhook**

**Webhook** is suitable for sending alerts to group bots, third-party systems, or a unified notification platform.

| Configuration Item | Description |
| - | - |
| **Webhook URL** | Enter the Webhook URL for receiving alerts. |
| **Remark** | Describe the purpose of the notification target for easier future maintenance. |
| **Language** | Select the display language for alert messages. |
| **Visible Scope** | **Only Self** means the target is available only to its creator; **Public** means it can be reused within the same tenant. |
| **Enabled** | Controls whether this notification target is used for sending alerts. |
| **Template** | Configure the Webhook request body template. For template syntax, see [Configure a Webhook Template](#configure-a-webhook-template). |

Webhook notification targets support only event alerts and metric alerts. If bound to other types of alerts, creation or delivery may be rejected, with the message: `webhook notification method is only supported for trigger and metric_rule type alarms`.

**SMS**

**SMS Notifications** are suitable for receiving alerts directly via text message on a mobile phone.

| Configuration Item | Description |
| - | - |
| **Mobile Number for Receiving SMS Alerts** | Enter an 11-digit mainland China mobile number. Do not add the `+86` prefix. International numbers are not supported at this time. |
| **Remark** | Describe the purpose of the notification target for easier future maintenance. |
| **Language** | Select the display language for alert messages. |
| **Visible Scope** | **Only Self** means that only the creator can use it; **Public** means that it can be reused within the same tenant. |
| **Enabled** | Controls whether this notification target is used to send alerts. |

### 3. Create the Notification Target

Click **Dry-run** to verify that the current notification target is reachable. After the dry run succeeds, click **Create**.

The dry run only verifies connectivity to the notification target; it does not guarantee that actual alerts will be delivered successfully. Actual delivery also depends on the subscription filter criteria, whether the alert is triggered, and whether the Noise Control suppresses or aggregates it.

The same mobile number may be subject to an hourly sending rate limit. SMS messages exceeding the limit will be skipped, but Feishu notifications and webhook delivery will not be affected.

## Create a Contact Group

Contact groups are suitable for combining multiple notification targets into a single recipient.

1. Go to **Alarm > Notification Management**.

2. Select the **Contact Groups** tab.

3. Click **Create**.

4. Configure the contact group.

   | Configuration Item | Description |
   | - | - |
   | **Group Name** | The name of the contact group. It is recommended to reflect its purpose, such as the training job on-call group or the resource alert group. |
   | **Remark** | Describe the usage scenario or maintainer of the contact group. |
   | **Notify Targets** | Select the notification targets included in the group. If no notification targets are available in the group, the contact group cannot be used for effective delivery. |
   | **Enabled** | Controls whether the contact group can be used to send alerts. |

5. Click **Create**.

After it is created, you can select this contact group when creating an alert subscription.

## Create a Third-Party Application

Third-party applications are used to manage configurations for enterprise applications such as Feishu applications. Before creating a Feishu application message notification target, you may need to prepare an available third-party application.

1. Go to **Alarm > Notification Management**.

2. Select the **Third-Party Application** tab.

3. Click **Create**.

4. Configure the third-party application.

   | Configuration Item | Description |
   | - | - |
   | **Name** | The name of the third-party application. |
   | **Feishu Application** | The Feishu application identifier. |
   | **Feishu Application App Secret** | The Feishu application secret. Keep it secure and do not expose it in documentation, tickets, or public channels. |
   | **Enabled** | Controls whether the third-party application can be referenced by notification targets. |

5. Click **Create**.

Third-party applications are typically maintained by tenant administrators. Before creating a Feishu application message notification target, regular users must ensure that an enabled third-party application is available for reference within the tenant.

## Manage Notification Objects

After locating the target object under **Alarm > Notification Management**, you can maintain the configuration as needed:

| Action | Description |
| - | - |
| **Edit** | Modify the configuration and enablement status. After changing the recipient address, recipient, or application configuration, we recommend testing again. |
| **Delete** | Delete notification targets that are no longer in use. Before deletion, ensure that the relevant subscriptions have been changed to use other delivery targets. |

## Configure a Webhook Template

A Webhook notification target can send alerts to group bots, third-party systems, or a unified notification platform.

When creating a Webhook notification target, you can customize a JSON request body template. The platform replaces template variables with alert data and sends a POST request to the Webhook URL.

The following top-level variables are supported:

* `{{ .Content }}`: The complete content of the alert, which may be a JSON object or a string.
* `{{ .AlarmTime }}`: The time when the alert occurred, for example, `2025-12-05T06:52:04Z`.

In addition to the complete object, you can also directly reference second-level fields in `{{ .Content }}`. Available fields may vary by alert type. For the full set of variables, refer to the template configuration prompts in the console.

| Variable | Description |
| - | - |
| `{{ .Content.alarmName }}` | Alert name. |
| `{{ .Content.summary }}` | Alert summary. |
| `{{ .Content.description }}` | Alert description. The original text may contain links. |
| `{{ .Content.descriptionText }}` | Plain-text alert description. |
| `{{ .Content.level }}` | Alert severity. |
| `{{ .Content.severity }}` | Alert severity level, such as `critical`, `warning`, or `info`. |
| `{{ .Content.status }}` | Alert status, such as `firing` or `resolved`. |
| `{{ .Content.bizId }}` | Business ID. |
| `{{ .Content.cluster }}` | Cluster name. |
| `{{ .Content.region }}` | Region name. |
| `{{ .Content.location }}` | Location information, such as region / cluster. |
| `{{ .Content.orgName }}` | Tenant name. |
| `{{ .Content.user }}` | User name. |
| `{{ .Content.workloadType }}` | Workload type. |
| `{{ .Content.workloadId }}` | Workload ID. |
| `{{ .Content.resourcePool }}` | Resource pool identifier. |
| `{{ .Content.generator }}` | Details page URL. |
| `{{ .Content.alarmTime }}` | Alert time, equivalent to `{{ .AlarmTime }}`. |

Send to a custom service and include complete alert data:

```json theme={null}
{
  "msg_type": "alarm",
  "data": "{{ .Content }}",
  "timestamp": "{{ .AlarmTime }}"
}
```

Send to a DingTalk, WeCom, or Feishu custom bot, and concatenate into a text message:

```json theme={null}
{
  "msg_type": "text",
  "content": {
    "text": "Alert triggered!\nDetails: {{ .Content }}\nTime: {{ .AlarmTime }}"
  }
}
```

The receiver should parse the request body as standard JSON. After creating or modifying a template, test delivery before binding the notification target to an alert subscription.

## Next Steps

* [Create Alarm Subscriptions](/siverse/alerts/create-alert-subscriptions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.