Serverless App Engine:Manage contacts

Create a contact

Navigate to the contact management page first: log in to the SAE console, go to Applications > Applications, select your region and namespace, click an application name, and then choose Notifications and Alerts > Contact Management in the left-side navigation pane.

1. On the Notification Objects page, go to the Contacts tab and click Create Contact.

2. In the Create Contact dialog box, fill in the contact details and click OK.

   Specify at least one of Phone number or Email. Each phone number and email address can belong to only one contact. To set up a DingTalk chatbot, use the DingTalk/Lark/WeCom tab instead.

   Parameter	Description
   Name	The name of the contact.
   Phone number	Enables phone call and text message notifications. Only verified phone numbers can be used in a notification policy. See Verify phone numbers.
   Email	Enables email notifications.
   Contact group	The contact group to add this contact to. See Create a contact group.
   Method to resend notifications if phone notifications fail	The fallback method when a phone call fails. Set a global default for all contacts under More > Contact Default Configuration on the Contacts tab.
   User ID	An identifier used for data processing and queries.

After creating a contact, search for, edit, or delete it on the Contacts tab.

Verify phone numbers

Phone numbers must be verified before they can be used in a notification policy. The verification code is sent to the phone number being verified — contacts must have access to that number to complete verification.

1. On the Contacts tab of the Notification Objects page, select the contacts whose numbers you want to verify: SAE sends a text message with a verification link to each selected number.

   • To verify a single number, find the contact and click Not Verified next to the phone number.

   • To verify multiple numbers at once, select the contacts and click Batch Verify.

2. Each contact opens the URL from the text message in a browser.

3. On the verification page, the contact checks the number and clicks Verify.

Set the default fallback method

When a phone notification fails, SAE uses a fallback method to resend the alert. Set a global default for all contacts:

1. On the Contacts tab of the Notification Objects page, choose More > Contact Default Configuration.

2. Select the fallback method and click OK.

Individual contacts can override this default using the Method to resend notifications if phone notifications fail parameter when creating or editing a contact.

Prerequisites

At least one contact must exist. See Create a contact.

Create a contact group

1. On the Contacts tab of the Notification Objects page, click Create Contact Group.

2. In the Create Contact Group dialog box, enter a name in Group Name, select contacts from the Alert Contacts list, and click OK.

The contact group appears in the All Contacts list on the Contacts tab.

Manage a contact group

After creating a contact group, manage it from the Contacts tab:

Action	Steps
Edit	Click > Edit Group to the right of the group. Modify the name or members, then click OK.
View members	Click the icon to the left of the group.
Delete	Click > Delete Group to the right of the group, then confirm.

Prerequisites

A DingTalk group with a custom chatbot added, and the chatbot's webhook URL. See Get the webhook URL of a DingTalk chatbot.

Add a DingTalk chatbot

1. On the Notification Objects page, click the DingTalk/Lark/WeCom tab, then click DingTalk.

2. In the Create DingTalk chatbot panel, configure the parameters and click OK.

   To receive alerts in a DingTalk group, set Notification methods to DingTalk in the notification policy. See Configure a notification policy.

   Parameter	Description
   Name	A name for the DingTalk chatbot.
   Signature key	Optional. If specified, DingTalk authenticates requests using the signature key. If left blank, authentication uses a whitelist with the keyword Alert.
   Chatbot webhook URL	The webhook URL of the DingTalk chatbot.
   Whether DingTalk chatbot sends daily statistics	If enabled, enter the times to send daily summaries. Format: HH:SS, comma-separated. Each summary includes the total alerts generated that day, resolved alerts, and outstanding alerts.
   Card content configuration	Customize the style and content of the alert notification card.

Manage alerts in a DingTalk group

After receiving alert notifications in the DingTalk group, view and manage them directly in the group. For details, see Handle alerts in the specified group chat.

Step 1: Get a webhook URL

1. Open Lark and log in.

2. Click + > New group to create a group for receiving alerts.

3. Open Group settings, go to the BOTs tab, and click Add Bot.

4. Select Custom Bot, set a name and description, and click Add.

5. Copy the webhook URL. Under Set keywords, enter Alert and click Save.

Step 2: Create a webhook in SAE

1. On the Notification Objects page, go to the Webhook Integration tab and click Create Webhook.

2. In the Create Webhook panel, configure the parameters. Notification template example (Lark):

   Parameter	Description
   Webhook name	A name for the webhook.
   Post/Get	The request method. The URL cannot exceed 100 characters. For Lark, select Post and paste the webhook URL from Step 1.
   Header/Param	Additional request headers or parameters. Maximum 6 entries total; maximum 200 characters combined. The default header is Content-Type: text/plain; charset=UTF-8. For Lark, add Arms-Content-Type: json and Content-Type: application/json.
   Notification template	The message body sent when an alert fires (POST only). Use $content as a placeholder for alert content. Maximum 500 characters. See Configure a notification template and a webhook template.
   Template to clear alerts	The message body sent when an alert resolves (POST only). Maximum 500 characters.

   {
     "msg_type": "text",
     "content": {
       "text": "Alert name: {{ .commonLabels.alertname }}\n{{if .commonLabels.clustername }}Cluster name: {{ .commonLabels.clustername }}\n{{ end }}{{if eq \"app\" .commonLabels._aliyun_arms_involvedObject_kind }}Application name: {{ .commonLabels._aliyun_arms_involvedObject_name }}\n{{ end }}Notification policy: {{ .dispatchRuleName }} \nAlert time: {{ .startTime }} \nNotification content: {{ for .alerts }} {{ .annotations.message }}\n {{ end }}"
     }
   }

   Template to clear alerts example (Lark):

   {
     "msg_type": "text",
     "content": {
       "text": "Alert name: {{ .commonLabels.alertname }}\n{{if .commonLabels.clustername }}Cluster name: {{ .commonLabels.clustername }}\n{{ end }}{{if eq \"app\" .commonLabels._aliyun_arms_involvedObject_kind }}Application name: {{ .commonLabels._aliyun_arms_involvedObject_name }}\n{{ end }}Time when the alert is resolved: {{ .endTime }} \nNotification policy: {{ .dispatchRuleName }} \nNotification content: {{ for .alerts }} {{ .annotations.message }}\n {{ end }}"
     }
   }

3. Click Send Test to verify the webhook is working, then click OK.

   The webhook has a 5-second timeout. If no response is received within 5 seconds, the notification fails.

Step 3: Attach the webhook to a notification policy

When creating or editing a notification policy, set Notification object to Universal Webhook and select your webhook. For details, see Configure a notification policy.