Find the cause of Kubernetes workload failures.
What it does
Diagnoses Kubernetes failures and provides an evidence-backed root-cause hypothesis with recommended next steps.
When to use it
Use when diagnosing pod failures, node pressure, resource exhaustion, image pull failures, admission rejections, autoscaling anomalies, or Kubernetes/application signal correlations.
How to use it
Give it a Kubernetes incident question or supplied evidence; it returns a hypothesis, supporting evidence, confidence, and recommended next steps.
Uses
What you need · 4
Cluster queries require elastic CLI version 0.2 or later with an Elasticsearch context; analysis of evidence already supplied by the user does not require cluster access.
Cluster queries require Elasticsearch 8.11 or later, or Serverless, with Kubernetes telemetry ingested through EDOT / the OpenTelemetry kube-stack collector into OTel-receiver-namespaced data streams.
Access · 2
This skill
Elasticsearch
Reads Kubernetes telemetry from Elasticsearch
Kibana
Reads enabled alert rules