After you configure an instant messaging (IM) channel, health check reports and alert diagnostics from the Task Center are sent directly to a DingTalk group. Your team can then see the instance status and recommended actions without logging on to the console. This topic describes how to configure a channel, how to plan the scope of notifications, and the security requirements involved.
Scenarios
IM channels bring diagnostic results from the console into your team workflow. Common use cases are as follows.
Scenario | Recommended recipient group |
Production alert diagnostics | On-call group or core operations group |
Daily or weekly health check reports | Platform operations group or governance group |
Slow SQL governance | Data engineering or application development group |
Ingestion errors and data freshness issues | Data pipeline group |
Configuration verification and feature testing | A separate test group that is not shared with production |
Prerequisites
A custom chatbot is created in the target IM group, and you have obtained its webhook URL and signature key. For DingTalk, add a custom chatbot in the group settings to obtain both values.
Configure an IM channel
Log on to the EMR console.
In the left-side navigation pane, click EMR AI Assistant, and then click IM configuration.
Add a channel and configure the following parameters.
Parameter
Description
Recommendation
Channel name
Identifies the notification target in the task configuration.
Include the environment, workload, and purpose, such as "Production - real-time warehouse - on-call".
Channel type
The IM service used for notifications.
Select DingTalk.
Webhook
The endpoint that receives messages for the group chatbot.
Copy the value from the chatbot settings and handle it as sensitive information.
Signature key
The credential used to verify requests sent to the group chatbot.
Keep it consistent with the chatbot settings. Do not store it in shared documents or code repositories.
Save the channel configuration.
Return to Task Center and set the notification channel of a health check task or an alert task to this channel.
Click Run now to trigger the task once, and then confirm that the message arrives in the group.
Channel planning
Avoid creating too many channels, but do not send every task to the same group either. Splitting channels by recipient and content type reduces unnecessary interruptions.
Channel | Recipients | Content |
Production alert group | On-call engineers, SREs, and service owners | High-risk alerts and incident diagnostics |
Routine check group | Platform operations engineers and DBAs | Health check summaries and health trends |
Governance group | Data engineers and application developers | Slow SQL, ingestion, and materialized view governance items |
Test group | Engineers who verify features | Webhook connectivity and task configuration tests |
Notification content and security requirements
Everyone in the group can see the content that is sent to it, so control the scope of the information.
We recommend that you send the task name, instance, run time, status, risk level, key conclusions, recommended actions, and a link to the full report.
Do not send complete sensitive SQL statements, unmasked logs, credentials, account information, or detailed business data. To read the full report, use the link to return to the console.
The webhook URL and the signature key are sensitive information. Observe the following requirements.
Do not paste the webhook URL or signature key into an EMR AI Assistant conversation, a group announcement, or a code repository.
Configure separate channels for production and test environments so that test messages are not sent to a production group.
Review the recipients after the group membership changes, and confirm that the alert content remains visible only to the intended audience.
If you suspect that the webhook URL is exposed, reset the chatbot immediately and update the channel configuration in the console.
FAQ
What do I do if no message arrives after I create a channel?
Check the following items in order: whether the task is associated with the channel, whether the task ran successfully, whether the webhook URL is correct, whether the signature key matches the chatbot settings, and whether the chatbot is enabled. You can view the run status and the notification status in execution history.
Can one channel be associated with multiple tasks?
Yes. However, we recommend that you split channels by environment and alert severity so that high-priority alerts are not mixed with routine reports.
Can I send the full diagnostic report to a group?
We recommend that you send only a summary and a link. If the report contains sensitive SQL statements, logs, or configurations, restrict its visibility or mask the data first.