Bot uptime monitoring
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 305
- Forks
- 148
- Avg merge
- 9h 2m
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the bot's production deployment and available integration points, then compare the monitoring options listed in the issue. Done should include an agreed monitoring approach for uptime and response time, with its operational requirements defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100