3 ms·
Very true, at the individual error level. That said, Fastly fixed the entire issue in less time than it would have taken AWS to update the status page to the bl
by QuinnyPig 5y ago
Very true, at the individual error level. That said, Fastly fixed the entire issue in less time than it would have taken AWS to update the status page to the blue diamond, so there’s that.
- WatchDog 5y ago"Service is experiencing increased error rates" - Error rates increased from 0 to 100%
- slver 5y agoNo service has 0% error rate, and 100% errors doesn't even mean much without context (you never receive all possible errors at once).
- jfrunyon 5y agoError rate = (number of requests which returned an error) / (total number of requests) You can choose plenty of time periods to satisfy a 0% error rate for most services - somewhere from milliseconds to days or even years.
- sharken 5y agoOr 50% error rates in case one of two nodes is down and you keep calling the faulty node. But the faulty node should not be called in a well designed system.
- dijit 5y agoBut then you're serving 100% faulty. Error rates (as alert thresholds and end user reporting) are a service thing, not a node thing.
- Xorlev 5y agoIn large organizations, status boards are "external communications" and this must be handled by a team dedicated to that. It works about as well as you might expect.