Observability K8s Investigation

When your Kubernetes pods are crashing or your nodes are under pressure, this skill correlates OTel telemetry from EDOT's kube-stack collector to find the root cause. It pulls from kubeletstats, k8scluster, and k8sevents receivers to connect runtime metrics, cluster state, and Kubernetes events. The documentation is refreshingly honest about common misdiagnoses: it warns you that OOMKilled doesn't automatically mean memory leak, that average CPU hides throttling pain, and that empty results mean missing data, not healthy systems. It's scoped strictly to the OTel ingestion path and explicitly excludes the legacy Elastic Agent integration, so you won't waste time querying deprecated indices.