Production Debugging Playbook: a six-step method to find the real cause of 5xx spikes
_jaydeepkarale · x · 2026-10-21
Engineer @jaydeepkarale's Production Debugging Playbook Part 2 covers a systematic approach to 5xx spikes — the error is a symptom, and the service returning it may not be the one causing it: (1) scope impact via error rate vs traffic, affected endpoints/regions/versions, recent deploys; (2) trace the failing request across gateway, app, and dependencies (e.g., a 502 from Product Service that's really a Pricing Service timeout); (3) interpret status codes — 500 app exception, 502 bad upstream response, 503 overload/unavailable, 504 gateway timeout; (4) validate the root cause with evidence from traces, logs, and metrics before fixing; (5) apply a targeted fix and verify recovery. Part 1 of the series covers debugging high latency starting from p50/p95/p99 percentiles rather than averages.
More from coding & agent
- Sentence Transformers 6.2.0 adds Python 3.14 support with two upgrade caveats — tomaarsen · 2026-10-21
- Sentence Transformers 6.2.0 fixes FP16 pooling arithmetic, speeds up CPU semantic search — tomaarsen · 2026-10-21
- Sentence Transformers 6.2.0 improves multi-vector models with finer compression control — tomaarsen · 2026-10-21
- Sentence Transformers 6.2.0 cuts training memory with quadratic/linear loss storage — tomaarsen · 2026-10-21
- Sentence Transformers 6.2.0: DDP eval sharing and 43-61% faster cached model loading — tomaarsen · 2026-10-21
- How SentenceTransformer.merge works: compatible architectures in, trainable model out — tomaarsen · 2026-10-21