Post #2105900

@yosh @menos I don't think it's "the one true way to talk about uptime" but "percent of time the system is not degraded" is something people care about. Let's call them AND-uptime and AVG-uptime. AVG-uptime is a better representation of how the component services doing, but AND-uptime is a better measure of how the system as a whole is doing. Especially, because many use cases will break if any part of the workflow does. If I'm trying to land a PR (git-ops) that runs actions where some steps use the API and load packages, I'm dependent on like 4+ of these services and the AND-uptime of them matters to me.