How can I correlate Datadog Agent metrics with Kubernetes pod resource usage to diagnose performance bottlenecks?

Understanding application performance often requires linking host‑level metrics gathered by the Datadog Agent with fine‑grained container resource usage from Kubernetes. Teams want to identify whether CPU or memory throttling at the pod level correlates with spikes in request latency or error rates observed in APM traces. However, it is unclear which Agent configuration options provide the necessary container metrics without introducing excessive overhead, and how version differences between Agent v6 and v7 affect metric availability.

What Agent settings enable collection of per‑container CPU, memory, and network I/O? How should these metrics be aligned with Datadog APM traces to produce a unified latency‑resource view? Which default dashboards or custom queries best reveal correlation between pod resource saturation and application performance degradation?