Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

高可用优化建议及通用性建议 #50

Closed
minibear2333 opened this issue Aug 13, 2020 · 4 comments
Closed

高可用优化建议及通用性建议 #50

minibear2333 opened this issue Aug 13, 2020 · 4 comments

Comments

@minibear2333
Copy link
Contributor

  1. 引入SQLite来本地存储模板,不方便扩展成多实例,要不要考虑去掉或者增加开关?
  2. 接入的数据格式默认是prometheus,其他服务不太方便接入,考虑增加更通用的接口?
  3. 没有失败重试或日志的功能
@feiyu563
Copy link
Owner

1.高可用方面,下一版本准备提供MySQL和sqlite两个选项
2.接入的数据其实提供了很多接口,目前全能的接口主要是自定义模板接口
3.失败重试方面确实还没集成的很好,这个后期会逐步优化,日志后期也会继续优化

@Zhang21
Copy link
Contributor

Zhang21 commented Sep 30, 2020

@feiyu563 @minibear2333 失败重试,程序要怎么判断呢?异步的化,不好判断返回状态。

我刚刚去看了一下alertmanager的通知,它有一个notify: https://github.com/prometheus/alertmanager/blob/master/notify/notify.go 来做这个事情。

@feiyu563
Copy link
Owner

feiyu563 commented Sep 30, 2020

失败重试主要针对消息接收端,比如短信电话这些,一般都有回调接口查询发送状态,目前重试只有腾讯语音有这部分逻辑

@feiyu563
Copy link
Owner

4.3版本已经更新支持mysql作为存储

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants