Bot uptime monitoring
未关闭
还没有人认领这个 Issue。
enhancement
- 主要语言
- JavaScript
- 星标
- 305
- 派生
- 148
- 平均合并
- 9 小时 2 分钟
- 30 天内合并 PR
- 3
描述
As this bot moves into production and starts getting integrated in various flows where people start depending on it, I think it is time to think about how we can monitory uptime and response-time of the bot.
Here are some suggestions which I have experience with:
| Name | Price | License | Remarks |
|---|---|---|---|
| Pingdom | $14.95/mo | ❌Proprietary | Easy to set up, but expensive 😕 |
| Pagerduty | $9/mo | ❌Proprietary | Very advanced. Much enterpizy 😐 |
| fzaninotto/uptime | Free | ✅MIT | Unfortunately this project is not maintained any more 😢 |
| DIY | Free | ✅MIT | Make something our self similar to what I have made for monitoring Jenkins Slaves |
We could send a shout out to Pingdom and Pagerduty to hear if they would like to sponsor the Node.js Foundation – it might be worth a shot.
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
调研方向
该 issue 未指定任何文件、测试或入口点。首先检查 bot 的 production deployment 和可用的 integration point，然后比较 issue 中列出的 monitoring 选项。完成标准应包括：为 uptime 和响应时间确定一种经过一致同意的 monitoring 方案，并定义其运维要求。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, nodejs
- 领域
- observability
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100