Message center and notification configuration-STAROps(STAROps)-阿里云帮助中心

STAROps sends notifications when a Mission event occurs, such as an AI assistance request (HIL), a completed report, or a Task error. You can configure notification channels, customize notification types, and respond to HIL (Human in the Loop) requests.

Notification channels

Mission events can be delivered through the following notification channels:

Channel	Description
Contact	Sends notifications to specified contacts by phone number or email.
Bot	Supports DingTalk, Lark, Slack, WeCom, and Teams. Pushes notifications to a group chat through a webhook URL.
Custom Webhook	Pushes notifications to a custom webhook URL for integration with self-built systems or third-party platforms.

Configure notification channels

You can configure notification channels from the Mission details page:

On the Mission details page, click the settings icon in the upper-right corner to open the settings panel.
In the Notification method area, click Go to Notification Management.
On the Notification Management page, select a notification channel and complete the configuration.

The following table describes the configuration for each channel:

Channel	Configuration instructions
Contact	Enter the phone number or email address of the contact.
Bot	Select the bot platform (DingTalk, Lark, Slack, WeCom, or Teams) and enter the corresponding webhook URL.
Custom Webhook	Enter the custom webhook URL.

Example: Configure DingTalk notifications

In your DingTalk group, add a custom bot and obtain the webhook URL. For details, see the DingTalk custom bot documentation.
On the Mission details page, click the settings icon in the upper-right corner to open the settings panel.
In the Notification method area, click Go to Notification Management.
Configure the DingTalk notification channel. For details, see Notification object.
Verify the configuration. In the conversation input box, enter: View current notification contacts.
Select the notification method using one of the following approaches:
- Option 1: Use the configuration page. For Missions with no notification channel, after the AI responds, a prompt appears: "This Mission has no notification channel. Configure now." Click Configure now to select a channel.
- Option 2: Configure through conversation. In the conversation input box, enter a request such as: Summarize the inspection results every 2 hours and send the summary to DingTalk bot xxx.
  
  The AI configures a scheduled task and a notification channel based on your request.
Click Settings to view the configured notification channels.

Recommended notification configurations

Scheduled delivery
Every 2 hours, summarize the inspection results for that period and send them to xxx.
Every Friday, summarize the week's inspection results and send them to DingTalk contact xxx.

Event-triggered notifications
During inspection, if CPU usage exceeds 80%, immediately notify xxx.
During inspection, if a Pod enters CrashLoopBackOff or restarts more than 3 times within 30 minutes, send an SMS to xxx immediately.

Modify notification contacts
The current notification contact is no longer valid. Update the notification contact to send future notifications to DingTalk contact xxx.
Remove the current contact and send notifications to xxx.

Cancel notifications
Remove the current notification contact: xxx.
Cancel the current notification contact: xxx.

Notification types

The following notification types are generated during Mission execution:

Type	Trigger	Description
HIL request	The AI needs a user decision or additional information.	The AI sends the request through both the conversation interface and configured notification channels.
Report generated	A Task completes and a report is generated.	You can view the report on the Reports tab of the Mission details page.
Task error	A Task fails or times out.	Includes the failure reason for timely investigation.

View and respond to HIL requests

When the AI needs your input during Mission execution, it sends a request in the Mission conversation interface and notifies you through the configured channels. You can view and respond to the request in the conversation area on the Mission details page.

For details about HIL request confirmation options and the human-in-the-loop (HIL) mechanism, see Mission execution and human intervention.