3 ms·
For simplicity, you could use the fraction of api calls that our service level objectives. Google/SRE calls it "aggregate availability". https://landing.google.
by joshuanapoli 6y ago
For simplicity, you could use the fraction of api calls that our service level objectives. Google/SRE calls it "aggregate availability". https://landing.google.com/sre/sre-book/chapters/embracing-risk/#risk-management_measuring-service-risk_aggregate-availability-equation https://landing.google.com/sre/sre-book/chapters/embracing-r...
- foxtr0t 6y agoYeah, this problem has a pretty obvious solution that is implemented by many teams: find a unit of work that we can measure success and failure over, report an aggregate metric over a specified time interval for availability tracking and plotting: # units successful / total # of units
- a1369209993 6y agoTo be fair, that has problems like counting "do this thing; do that thing" twice as much as "do these four things" rather than vice-versa. Still useful though.