The same count for another SLO — for part of the requests and with a strict target.
Orders and the cart matter more to the shop than the home page, and for them the team keeps a separate target, stricter than the overall one. There are about half as many requests to /api/, and the allowed share of errors is five times smaller, so the budget of such an SLO is ten times smaller too. An outage the overall SLO survived may be too much for the separate target. The request path is field $7, as in the lesson on SLIs.
Check the budget of orders and the cart
Orders and the cart have their own SLO — 99.9 % good answers for the /api/ addresses over 30 days. Count what is left of its budget and put one number in ~/slo/api.txt; an overspend is a negative number.
Goals · 0 of 1
- Put what is left of the /api/ SLO budget in ~/slo/api.txt not done yet