Sample finding
From the findings report · Request paths
Illustrative example
Retries at three layers can turn one slow dependency into an outage.
Evidence
The ingress, the mesh, and the checkout service's HTTP client each make up to three attempts, so one request can reach the payments API 27 times. The ingress gives up first, after 15 seconds.
ingress configmesh policytraces
Impact
When the payments API slows, retries multiply its load until it fails outright, while it keeps working on requests users have already abandoned.
Priority
High
Checkout carries revenue, and the fix is configuration only, so it fits the next scheduled maintenance window.
Recommended next step
Let only the mesh retry, with a retry budget, and give each layer a shorter timeout than the one in front of it. Prove it with a fault-injection test.
Alternative consideredRetrying in each client library instead gives finer control per call, but every service team then maintains its own settings. We recommend it only for calls that leave the mesh.