Collect e-mails before being sent
还没有人认领这个 Issue。
评估
调研方向
该 issue 未指出需要检查的文件、测试或入口点。首先定位通知和资源检查的调度路径，然后定义批处理间隔、立即失败时的行为、恢复处理方式，以及用于证明通知在不丢失状态变化的情况下进行分组所需的测试。
由索引模型根据 Issue 内容生成。
描述
Currently, GHC sends an e-mail whenever a resource check fails, and also when the resource check is working again. This is the case when you've set GHC_NOTIFICATIONS_VERBOSITY to False. With this variable set to True, you'll probably get even more e-mails.
I was performing a test with a large number of resources (close to 1000) and with a short test interval (every 5 minutes). The server being tested had some trouble coping with this test, so this was more a load test than a monitoring test. As a result GHC started sending a lot of e-mails, until a limit imposed by my provider was hit. This was worsened by the fact that earlier today a lot of tests failed due to wrong credentials being sent (HTTP 401 errors).
Would it be a good idea to have an option with which GHC can batch status reports and send them only after an interval has passed? For example, every minute, or every 5 minutes. Of course this means that the delivery of mails notifying the administrator of failures has a delay, so sending this interval too high is not advisable. Perhaps the first mail could be sent immediately, and any other mails within this interval could be batched.
Regarding my test: foremost this was just a test, but it made me think about differentiating between the type of checks which should be done. Some checks which have been added are meant to check the availability, where as other checks are meant to do more in depth checks on the content. The former checks could be performed at a higher interval than the latter. Nonetheless, I'm seeking a solution where I won't be hit by the limit imposed by my provider.
- 主要语言
- Python
- 星标
- 92
- 派生
- 77
- 平均合并
- 5 小时 37 分钟
- 30 天内合并 PR
- 4
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
geopython/GeoHealthCheck 的其他 Issue
-
Data import未关闭question
难度 4/5 3-5 天 新手友好度 38/100
geopython/GeoHealthCheck#522 · 1 条评论 ·
-
FTP Probe未关闭enhancement
难度 4/5 3-5 天 新手友好度 48/100
geopython/GeoHealthCheck#520 ·
-
bug
难度 3/5 1-2 天 新手友好度 55/100
geopython/GeoHealthCheck#517 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 45/100
geopython/GeoHealthCheck#483 · 1 条评论 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 35/100
geopython/GeoHealthCheck#472 ·
查看 geopython/GeoHealthCheck 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
Status: Triaged Type: Enhancement
难度 1/5 1 小时以内 新手友好度 82/100
canonical/craft-store#448 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
good first issue research size:s skill:numerics sub-issue
难度 2/5 1-3 小时 新手友好度 78/100
SKaiNET-developers/SKaiNET#1372 ·
维护者通常 1 天内回复
-
debt
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/vscode-flake8#601 ·
维护者通常 1 天内回复