Hacker News Reader

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.

View on HN

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).

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.

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.

I agree 100%. That column of uniform green makes it easy to miss. It is a poor UI choice but can be easily fixed.

However it is hard to miss the difference in the column with details and the more link even upon a cursory scan.

Reply on news.ycombinator.com