I think the alert module can be retained. Currently, it only supports email and webchat, but more alarm modes can be added in the future.
At present，alert is a independent service. the alert service only consumes alarm information in the database, other services produce these alarm information. If a new alarm mode is added, It is only necessary to redeploy the alert service. ________________________________ DolphinScheduler(Incubator) PPMC Gang Li 李岗 [email protected]<mailto:[email protected]> 发件人： qiao zhanwei<mailto:[email protected]> 发送时间： 2019-12-10 14:24 收件人： dev<mailto:[email protected]> 主题： Aproposal for DolphinScheduler Simplified Deployment Hello All , Now DolphinScheduler has so many Configuration files for example : dolphinscheduler-alert : alert.properties dolphinscheduler-api : application-api.properties application-combined.properties dolphinscheduler-common : hadoop.properties common.properties quartz.properties zookeeper.properties dolphinscheduler-dao : application-dao.properties dolphinscheduler-server : application-master.properties application-master.properties master.properties worker.properties .dolphinscheduler_env.sh Can we simplify deployment ? Main point : 1 configuration file simplification and merged configuration file 2 master server remove port 3 support offline installation，remove kazoo dependencies in install and monitor 4 instll.sh script simplification ――――――――――――― DolphinScheduler(Incubator) PPMC Zhanwei Qiao 乔占卫 [email protected]
