Re:Summary of the Amazon DynamoDB Service Disruption
by deanCommie on Wednesday September 23, 2015 @12:04PM
(#10265863)
The question of timing of the green-I is valid, but different from your original complaint.
In your hypothetical scenario, the customer that is going to the panel to "find out what the fuck is going on" is not going to miss the indicator i, and will read the description of the message.
Re:Summary of the Amazon DynamoDB Service Disruption
by toomuchtodo on Wednesday September 23, 2015 @12:45PM
(#10266154)
I don't care what that "i" indicator is; if you're showing green while you're impacted, your status board is useless and I'm going to Twitter and HN to see if you're broken (which is what I already have to do for AWS).
Re:Summary of the Amazon DynamoDB Service Disruption
by mgkimsal on Wednesday September 23, 2015 @08:19PM
(#10269145)
When we've seen problems, some of my clients go there and see green and say "Amazon shows they're fine - it must be your code or something you did or didn't do - fix it". Well... it's green but it's not fine. And there's little I can do to demonstrate to someone that it's not code but infrastructure.
Re:Summary of the Amazon DynamoDB Service Disruption
by RyanGWU82 on Wednesday September 23, 2015 @12:36PM
(#10266078)
It's really easy to miss the indicator "i". I've been doing this for 4 years and it still doesn't catch my eye when scanning the page.
Customers are totally not interested in the fact that some other random customer may not be experiencing problems and that amazon has a wide variety of services, some of which may not be affected in certain geographies. Customers go to that panel with one express goal: to discover if the problems they are seeing with their servers could be related to them. It is a triage check. The question is not, is Amazon super great and are the availability engineers the bestest on average over time? The question is, what the fuck is going on?
Amazon has suffered catastrophic unavailability, and the green-i has appeared belatedly, an hour or more into the problem. Because as revealed in this post, it is manually put up by engineers. Manually!
Manually!