container-monitoring

Query Kubernetes and Docker container metrics, pod status, and cluster health via Datadog APIs.

5|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/lauhon/pi --skill container-monitoring-lauhon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-monitoring
Source: https://github.com/lauhon/pi/tree/main/skills/container-monitoring
Command: npx skills add https://github.com/lauhon/pi --skill container-monitoring-lauhon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Monitoring Kubernetes clusters and Docker containers requires navigating dozens of metrics, APIs, and query syntaxes. This Skill provides a structured way to query container performance, track pod health, detect restart loops, and manage container monitors in Datadog without memorizing metric names or CLI flags. ## Core Features & Use Cases - Container & Kubernetes Metrics: Query CPU, memory, network, and disk usage for containers, pods, deployments, StatefulSets, and nodes using the pup CLI. - Cluster Health Diagnostics: Identify restarting pods, pending pods, OOMKills, crashloops, and deployment replica issues across namespaces. - Container Monitor Management: Search, inspect, and create Datadog monitors for container resource thresholds and pod failures. - Use Case: When a user asks "Which pods are restarting in production?", the Skill runs a grouped query on kubernetes.containers.restarts and returns a namespace-level breakdown with actionable recommendations. ## Quick Start Ask the agent to show container CPU and memory usage across your Kubernetes cluster for the last hour.

Frequently Asked Questions about container-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which Kubernetes pods are restarting?

Query the kubernetes.containers.restarts metric grouped by kube_namespace and pod_name over a recent time window such as 4 hours. A rising restart count typically indicates a crashloop, failing liveness probe, or resource limit issue.

How do I monitor container CPU and memory usage in Datadog?

Use the metrics query API with container.cpu.usage and container.memory.usage grouped by container_name. Compare actual usage against container.memory.limit to spot containers approaching their limits.

What is the difference between kubernetes.* and container.* metrics in Datadog?

kubernetes.* metrics come from the Kubernetes API and kubelet and reflect orchestration state, while container.* metrics come from the container runtime such as Docker or containerd. Use container.* for actual resource usage and kubernetes.* for pod and deployment status.

Does Datadog container monitoring support EKS, GKE, and AKS?

Yes, Datadog supports Amazon EKS, Google GKE, Azure AKS, OpenShift, Rancher, and self-managed Kubernetes. Deploy the Datadog Agent or Cluster Agent via Helm or the Datadog Operator with the container integration enabled.

Why am I getting no container metrics from Datadog?

Missing container metrics usually means the Datadog Agent is not installed on the hosts or the container integration is not enabled. Verify the Agent is running, the Docker socket is mounted, and containers are being discovered.

When should I use the Infrastructure agent instead of container monitoring?

Use the Infrastructure agent for host inventory tasks such as listing all hosts or counting hosts by environment. Container monitoring is scoped to container, pod, and Kubernetes workload metrics rather than general host inventory.