I want status pages to show traffic to the status page itself over the last 24 hours (or some time period). A sudden uptick in traffic but green across the board would indicate that there is an issue, but they just haven't updated the page yet.
Yes! I have yet to convince anyplace I've been working to do this, but I do make increases in traffic volume to status pages generate non-critical alerts. Has caught out a few problems much earlier than they otherwise would have been discovered.
Sounds like an interesting way to make developers (or ops) life hell. Just point a traffic cannon at the status page and bingo bango non-critical page.
Do you write every single test for your codebase? Do you have control over every line of code that gets deployed? The purpose of monitoring is to detect issues, because preventing them entirely is next to impossible.
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?)
I've always wanted to build a public status page for services like Google Cloud and AWS with real tests against different services they offer. Not sure there is a good way to monetize though.
Some of the AWS UX is okay but the parameter store UX for the web console is some of the worst I've seen. It's difficult to navigate and paginate, and the search function is barely worth using. It would be amazing if they had fuzzy search on the names.
I do agree that the CloudWatch console search is like this, where you need to type out the entire string from the beginning to get it to match. But for the CloudFormation and Lambda consoles, I can just type a piece of the string I'm trying to find and all matching will just show up.
The UX is a bit poor and there are long standing issues like the S3 console timeout bug and the SWF console not obeying any known law of web design but serious teams don't really use the console, they use tools like Terraform, CloudFront or they roll their own automation.
I use the AWS APIs almost every day but probably log in once a week or so.