apache / dolphinscheduler

Apache DolphinScheduler is the modern data orchestration platform. Agile to create high performance workflow with low-code
https://dolphinscheduler.apache.org/
Apache License 2.0
12.84k stars 4.62k forks source link

[Feature][Alert]Enterprise WeChat support send notifications by robot #14839

Closed ahuljh closed 3 weeks ago

ahuljh commented 1 year ago

Search before asking

Description

Chinese:经与企业微信论坛和官方客服确认,企业微信无法发送告警信息到已有的内部群,原因是无法获取到已经创建内部群的chatid,只能通过接口创建,必须要单独创建群聊,不满足实际需求。论坛上有许多人反映此问题,且经受困扰。同时,DolphinScheduler的贡献者群内也有相同的诉求。该问题亟待解决。 English: After confirmation with the enterprise WeChat forum and official customer service, it was found that enterprise WeChat cannot send alarm information to existing internal groups because it cannot obtain the chatid of the already created internal group. It can only be created through the interface and must be created separately, which does not meet actual needs. Many people on the forum have reported this issue and are experiencing difficulties. At the same time, there are similar demands within the contributor group of DolphinScheduler. This problem urgently needs to be solved.

Use case

经调研,可以通过在群内增加机器人的方式解决。我会新增加一种告警插件,以满足这个需求。 After research, it can be solved by adding robots to the group. I will add a new alarm plugin to meet this requirement.

Related issues

No response

Are you willing to submit a PR?

Code of Conduct

github-actions[bot] commented 1 year ago

Search before asking

Description

English: After confirming with the enterprise WeChat forum and the official customer service, the enterprise WeChat cannot send alarm information to the existing internal group, because the chatid of the internal group that has already been created cannot be obtained, and it can only be created through the interface, and the group chat must be created separately. Does not meet actual needs. Many people on the forum reported this problem and suffered from it. At the same time, DolphinScheduler's contributor group also has the same appeal. This problem needs to be solved urgently. English: After confirmation with the enterprise WeChat forum and official customer service, it was found that enterprise WeChat cannot send alarm information to existing internal groups because it cannot obtain the chatid of the already created internal group. It can only be created through the interface and must be created separately, which does not meet actual needs. Many people on the forum have reported this issue and are experiencing difficulties. At the same time, there are similar demands within the contributor group of DolphinScheduler. be solved.

Use case

After investigation, it can be solved by adding robots in the group. I will add a new alarm plugin to meet this requirement. After research, it can be solved by adding robots to the group. I will add a new alarm plugin to meet this requirement.

Related issues

No response

Are you willing to submit a PR?

Code of Conduct

ahuljh commented 1 year ago

image

image

imp2002 commented 1 year ago

It looks like just use webhook? DS alert has support it. https://developer.work.weixin.qq.com/document/path/91770

ahuljh commented 1 year ago

It looks like just use webhook? DS alert has support it. https://developer.work.weixin.qq.com/document/path/91770

Yes, I will use webhook to meet this demand. But DS don't have WebHook Alert Plugin. I will supply this plugin. image

qingwli commented 1 year ago

Could we use HTTP plugin for this feature?

ahuljh commented 1 year ago

Could we use HTTP plugin for this feature?

Yes, perhaps this is an indirect way of implementation. However, this increases the difficulty of use and requires offering many unnecessary parameters such as header and body. In fact, it is necessary to provide a simpler webhook plugin, which only requires a simple URL to provide.

github-actions[bot] commented 2 months ago

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] commented 3 weeks ago

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.