4 ms·
I often find out about these sorts of global internet issues early because of a little project of mine: https://statusgator.io https://statusgator.io It just
by colinbartlett 11y ago
I often find out about these sorts of global internet issues early because of a little project of mine:
https://statusgator.io https://statusgator.io
It just monitors the status pages of lots of different services. When I get 30 notices from various unrelated services at once all with comments like "Network connectivity issues", I know some kind of routing issue is plaguing the 'net.
- Goopplesoft 11y agoWhat do you use to monitor the status of the respective sites? Ping/head request to the site/api?
- colinbartlett 11y agoI actually don't monitor the status myself, I monitor the status that each service publishes. That is, whatever they report on their status page, StatusGator aggregates. The whole thing was born after I was racking my brain trying to debug a problem, then I remembered to check status.whatever.com and realized it wasn't my problem to debug and the provider was already aware of it. I thought it would be nice to get notifications as well as aggregate that info from all the different services I use.
- mawhidby 11y agoCool site! Any plans to add IBM Bluemix? Their status page is at https://developer.ibm.com/bluemix/support/#status https://developer.ibm.com/bluemix/support/#status
- colinbartlett 11y agoDone. Note a feature in the pipeline which will allow you to subscribe to specific components or specific regions of services. Which will make status notifications for large cloud platforms like Bluemix, Openshift, AWS, DigitalOcean, etc. much more useful.
- pliu 11y agoIn a situation like this, how do you know that routing to the status page is not the problem? Many of these companies use statuspage.io which is on AWS. Edit: this is an edge case, clearly. I just think it's an interesting problem.
- nthitz 11y agoWhat if statusgator.io or my routing to SG goes down? :)
- vacri 11y agoSame solution as every monitoring system: run a second, separate one. Whether it's the proverbial backhoe through the fibre link or a sysadmin fat-fingering a conf or deploy, there's always a way for a single system to be brought down. I saw an absolutely crazy way to do this with Nagios[1]. Nagios saves its state in a file, and the suggested way to synchronise two separate systems was to have them look to see if the other one is active. If it is, sync the statefile across. If it isn't, start up nagios locally based on the latest sync'd statefile. I mean, the solution works, but due to Nagios it's inherently hacky. It's bizarre that Nagios doesn't (didn't?) have inbuilt support for failover this way. [1]https://allmybase.com/2010/10/04/setting-up-fully-redundant-failover-nagios-servers/ https://allmybase.com/2010/10/04/setting-up-fully-redundant-...