Lightning Talk: Deep Dive Into Envoy Metrics

" summary

When 503s or 504s appear from an external ingress to the mesh check upstream_cx_connect_fail first to spot TCP connect failures, then correlate with tcpdump and tune connect_timeout; use upstream_rq_timeout for HTTP layer 7 timeouts and align upstream_cx_idle_timeout with backend idle settings. Inspect listener metrics like listener_destroy and listener_tls to verify ports and mTLS, compare membership_healthy with health_flags for control‑plane vs proxy view, watch Envoy CPU/memory as cluster count grows, and use XD snap to capture /stats and endpoints at intervals.

AI-written summary · about

" related talks

• 39mNetwork Observability with EnvoyNic Jackson · KubeCon + CloudNativeCon + Open Source Summit China 2019
• 39mNetwork Observability with EnvoyNic Jackson · KubeCon + CloudNativeCon China 2019
• 09mLightning Talk: The Hardest Part of Operating a Service Mesh: Envoy ProxyChristian Posta · ServiceMeshCon Europe 2021
• 33mEnvoy on Fire: A Practical Look at Debugging a Service MeshLita Cho, Ryan Cox · KubeCon + CloudNativeCon North America 2019
• 09mLightning Talk: Honey, I Broke the Things: Debugging Gray Failures in Production!Radha Kumari · EnvoyCon North America 2022
• 38mEnvoy Deep DiveMatt Klein · KubeCon + CloudNativeCon Europe 2018
• 01h 32mHands-on Workshop: Envoy Metrics Demystified WorkshopNic Jackson, Kerim Satirli · ServiceMeshCon North America 2022
• 10mLightning Talk: Envoy @ NetflixKevin Baichoo · EnvoyCon North America 2025