Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upBot uptime monitoring #63
Comments
|
Great initiative! It would be great to a least be confident it's up-n-running, which I guess the services you mention and Statuscake (free) could help us with. For response-time monitoring though, I'm not sure it'll be much value for those services to request a URL on the bot.. What we're really interested is the time it took to handle webhook requests from github.com or jenkins, and maybe how long the bot is waiting for third party APIs to respond (github, travis or jenkins). |
|
I think if we're to do such a thing we should look at the bigger scale for build resources. We have an email alert tool but we can improve lots here. |
|
@Starefossen perhaps we can expand the jenkins status monitor to do this check too? |
|
Yes, that would absolutely be possible! |
|
The bot already has a /ping endpoint which could be used? On Friday, 26 August 2016, Hans Kristian Flaatten notifications@github.com
|
|
@phillipj @Starefossen I run https://noty.im for uptime monitoring. We also have a chat bot to control from there(add check- ping endpoint, review stat) https://www.youtube.com/watch?v=z2o8DhoN0dg My whole stack is open source as well at github.com/notyim Let me know what I can do to help setting this up. |
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:
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.