5 ms·
I have worked at amazon, and I can validate this. When I was on an AWS team, posting a "non-green" status to the status page was actually a Manager decision. Th
by nhumrich 10y ago
I have worked at amazon, and I can validate this. When I was on an AWS team, posting a "non-green" status to the status page was actually a Manager decision. That means that it is in no way real time, and its possible the status might say "everything is ok" when its really not because a manager doesnt think its a big enough deal.
Also there is a status called green-i which is the green icon with a little 'i' information bubble. Almost everytime something was seriously wrong, our status was green-i, because the "level" of warning is ultimately a manager decision. So they avoid yellow and red as much as possible. So the status's aren't very accurate.
That being said, if you do see a yellow or red status on AWS, you know things are REALLY bad.
- toomuchtodo 10y agoDevops here who has to deal with the AWS status page frequently. Is someone's bonus or performance metrics tied to how often a service goes to "non-green" on the status page?
- nhumrich 10y agonot really. But the manager IS held responsible if they go green-i too often. As sometimes having a bad status can trigger AWS to give credits back to certain customers.
- cwillu 10y agoSounds like the green-i would be the better overall indicator to look at then? How reliable do you think it would be as an alternative?
- nhumrich 10y agoI mean, it's still a manager decision. So it usually goes green-i after you notice the issue. I would say it's the same, still not very reliable. But do know, that if you see the I indicator, something is wrong