It's annoying how often status pages for various services (when they even exist at all) show that things are working when they really aren't
Bit of a chicken and an egg problem :)
By your logic if you can write perfect integration tests, can't you write perfect application code that doesn't need to be tested?
OP is arguing that a perfect codebase is not possible, therefore it's a bit unfair to complain that the status pages do not work perfectly. Hence the chicken and egg problem of "if I could write a perfect status page, I would have skills such that the status page would not be necessary".
1) A guy with a button. It's right, but it requires the guy to notice or get told - and remember to push the button.
2) Automation. But your automation has to somehow catch bugs that you can't even dream of. And not be triggered randomly. And somehow be able to be automated but not fixed at the source (as if you know how something will fail - why not just fix that over adding more status checks?)
It looks like they are just an aggregator for status pages. I want something that does its own testing to determine if a service is up or down.
- Their products have weird names
- Their web console has horrible UX
- The lie about uptime and server status
I use the AWS APIs almost every day but probably log in once a week or so.