Solving Microservice Murder Mysteries with Envoy's Tap Filter
summary
Envoy’s Tap filter captures full HTTP request and response payloads when expressive match rules fire, writing files (default body limit 1 GB) or streaming to a service; demo shows it triggered on 5xx responses, produced a byte-encoded body that reproduces an intermittent failure and pinpoints the offending request (one of 324 possible failure paths). Config supports header-triggered captures, sidecar deployment, multiple tap specs, and upcoming fractional sampling; tooling built around it includes capture+replay workflows and projects like inloop for production capture and replay.
AI-written summary · about
related talks
21mDeep Dive: Envoy
33mEnvoy on Fire: A Practical Look at Debugging a Service Mesh
23mA Practical Guide to Understanding and Configuring Envoy Filters
33mIntro: Envoy
27mEnvoy - Overview and Update: Senior Envoy Maintainer
21mTap Tap, Debugging an App with your Service Mesh
33mIntro: Envoy
08mConnecting the (Proxy) Dots: A Beginners Guide to Reading Envoy Debug Logs