|· · ·|
|Open||None||T76375 New Labs project requests (tracking)|
|Resolved||Andrew||T148569 Request creation of community-labs-monitoring labs project|
|· · ·|
Oh, no. This is for specifically for Tool Labs and Labs instances. The intention here is to provide an easy way for volunteers to set up monitoring for their tools and labs instances.
My plan is to allow volunteers to log in via OAuth and "register" their tools and labs instances.
For the tools, I'm going to run HTTP checks - looking for a 200, 301, or 302. If I don't receive those, I'm going to generate an email sent to the tool email address.
For the Labs instances, I'm going to run ping and ssh checks. I'm looking for OK responses - if I don't receive them I'm going to generate an email also.
This is independent of any current checking system. iginga.wikimedia.org is blocked off for volunteers (Requires NDA as far as I know) and shinken doesn't monitor anything aside from the "tools" project instances (as far as I can tell - the interface for that tool is very convoluted)
Are there plans to expand shinken to tool labs? Running http checks?
Are there plans to allow volunteers to request shinken to monitor their instances?
I'm not being patronizing, I'm legitimately curious. Right now, I use Uptime Robot to monitor my tools on Tool Labs. I have no way of telling if a labs instance is "down," see comments of T148420 .
I'm attempting to fill a hole here - the ability for volunteers to set up in-house monitoring of their tools and labs instances. If there are plans to provide that functionality in the future, I will gladly close this task.
@Matthewrbowker the Labs operators discussed this a bit today. In general we /try/ to provide Labs monitoring tools but they're admittedly not so great, so you are welcomed (and encouraged) to work on alternatives.
That said, a more specific project name would be better -- 'status' is painfully vague. Thanks!