4 ms·
Not to mention the vitriol over a manually updated status page not updated the instant a service is down. I mean, the moment it went down I'm sure Github's SRE
by julianlam 5y ago
Not to mention the vitriol over a manually updated status page not updated the instant a service is down.
I mean, the moment it went down I'm sure Github's SREs were paged. Give them a minute to process it first, jeez.
- MrStonedOne 5y agoI have a status page that is automatically and manually updated and it costs 10 bucks a month to run, updates within 2 minutes of a downtime. Github has no excuse. We can and will hold them accountable for their decision to hide information from their paying customers and any other case they prioritize their ego over their users.
- Dylan16807 5y agoMockery, not vitriol. Nobody asked them to make it manual.
- naikrovek 5y agoit SHOULD be manual. you're foolish if you automate your red/yellow/green status indicators, or even host any of that kind of thing on your own infrastructure in any way. the status page needs to be updated by a human that knows what the issues are, and not automation that will flag everything red the instant anything trivial in the automation fails. you want static pages and images served up, nothing automated or scripted.
- Dylan16807 5y agoManual reporting tends to undershoot a lot. I find that worse than the risk of the status page going red when things are fine. > you want static pages and images served up Totally separate issue. You can update static pages with any method.