Connecting the (Proxy) Dots: A Beginners Guide to Reading Envoy Debug Logs
summary
Enables reconstructing a single request from Envoy’s noisy debug output by matching timestamps with connection id and stream id and following HTTP/2 pseudo‑headers, TLS handshake, and header mutations. Demonstrates a live log trace where the xdot filter issues a separate auth connection to localhost:8500 (POST, different stream id), Envoy builds a proxied upstream request, opens a new connection to a matched xDS cluster, receives a 200, and tears down the stream.
AI-written summary · about
chapters (4)
- 0:00Introduction to envoy logs
- 1:38Understanding log structure
- 2:53Tracing a request example
- 7:12Conclusion and takeaways
related talks
33mEnvoy on Fire: A Practical Look at Debugging a Service Mesh
39mNetwork Observability with Envoy
33mIntro: Envoy
01h 25mCloud-Native Building Blocks: An Interactive Envoy Proxy Workshop
09mLightning Talk: The Hardest Part of Operating a Service Mesh: Envoy Proxy
13mHoney, I Broke the Things: Debugging Gray Failures...
11mxDSnap: A Lightweight Tool to Debug Envoy and Consul Dataplanes with Confidence
09mLightning Talk: Honey, I Broke the Things: Debugging Gray Failures in Production!