In addition to the web interface, OAgent supports integration with messaging apps such as DingTalk, Lark, WeCom, and Telegram, facilitating collaboration with existing enterprise duty groups and automation workflows. The same private chat session can be continued across different IM channels; group/room sessions are isolated by channel.
Supported access channels
Channel |
Access Method |
Typical uses |
|---|---|---|
| Web Dialog | Browser Access to OAgent Frontend | Main entry for routine inspection, diagnostics, and tuning |
| DingTalk | Create a DingTalk chatbot and configure the callback | Alert linkage in the duty group and on-demand diagnostic initiation |
| Feishu | Create a Lark chatbot and configure the callback | Team Collaboration and Report Push |
| WeCom | Create an WeCom chatbot and configure the callback | Internal Q&A Group, Scheduled Task Result Push |
| Telegram | Create a Telegram Bot and configure its Token | Cross-region teams, mobile troubleshooting |
When to use
- After an alert is received in a duty group, @OAgent in the group to directly initiate root cause analysis without switching to the web.
- After a scheduled task generates a report, automatically push it to a specified IM group.
- Quickly check cluster status via Telegram on mobile devices.
Prerequisites
- OAgent has been correctly deployed and is accessible over the network by the target IM platform.
- You have the permission to create a bot or application on the target IM platform.
Procedure
In the left navigation bar, click Channels to go to the Channels page.
The page displays four fixed channel cards (DingTalk, Lark, WeCom, Telegram). Click Set Up Now on the target card and enter the access parameters for the selected channel.
Enter the access parameters for the selected channel:
DingTalkLarkWeComTelegramEnter the following parameters:
- Client ID (DingTalk AppKey): Obtained from the "Credentials and Basic Information" page after creating an enterprise internal application on the DingTalk Open Platform.
- Client Secret (DingTalk AppSecret): Obtained from the same page as Client ID. Keep it secure; if leaked, reset it on the Open Platform.
Enter the following parameters:
- App ID: Obtained from the "Credentials and Basic Information" page after creating an enterprise self-built application on the Lark Open Platform.
- App Secret: Obtained from the same page as App ID. Keep it secure; if leaked, reset it on the Open Platform.
Enter the following parameters:
- Bot ID: Obtained from the application details page after navigating to "Application Management → Self-Built → Create Application" in the WeCom Admin console.
- Secret: Obtained on the same page as the bot ID. Keep it secure. If it is leaked, reset it in the management console.
Enter the following parameters:
- Bot Token: Obtained after creating the bot with
@BotFather.
Click OK.
Usage
- Trigger a session in the IM according to the channel's convention (for example, @bot) to send commands. OAgent will orchestrate tools using the same logic as web and return conclusions.
- For scheduled tasks, you can choose to deliver results to a specified channel when creating the task. For more information, see Create a scheduled task.
- For some reporting skills, if the conclusion is too long, an abstract is automatically generated and a details link is provided in the session, allowing you to easily navigate to the report page to view the complete content.
What to do next
- You can monitor channel usage statistics. For more information, see Usage statistics.