Monitoring Network Traffic in Kubernetes
summary
Datadog shows concrete tools and outcomes: using AWS App Mesh with Envoy sidecars gives a central point of observability, and a new Datadog Network Performance Monitoring (GA tomorrow) watches layer 3/4 flows resolved to pod and service names. A trace example grows to 233 spans over 15 services and 16 hosts; a demo reroute triggers errors caused by insufficient pods visible as high TCP retransmits. Also offered is an open sourced watermark autoscaler used to reduce thrashing on a 2,500‑node cluster.
AI-written summary · about
chapters (7)
related talks
08mNetwork Performance Monitoring
44mKubernetes at Datadog Scale
34mHow to Survive to High Demanding Services
14mLeveraging Distributed Tracing in Kubernetes & Containerized Environments
34mHow to Survive to High Demanding Services
46mObservability in the real world: Improve systems w/iterative approach
44mChasing the Rainbow: Towards Unified Service Metrics
42mDistributed Monitoring: How to understand the Chaos
