Azure Kubernetes Service: pod name dimension on pod metrics retirement

From 30 Sep 2027, support for the pod name dimension is retired on the Azure Monitor platform metrics kube_pod_status_phase (number of pods by phase) and kube_pod_status_ready (number of pods in Ready state). After the change, the pod name dimension is not available for filtering, grouping, or alerting, while metric names stay the same, aggregate pod counts remain available, and namespace-level monitoring scenarios remain supported. Until the retirement date, AKS maintains both the existing and the new aggregate implementations, both are populated with data, and existing monitoring experiences continue to function. Dashboards, workbooks, alerts, automation, or monitoring workflows that filter, split or group these metrics by the pod name dimension may be affected.

1. Check whether any dashboard, workbook, alert, automation, or monitoring workflow uses kube_pod_status_phase or kube_pod_status_ready and filters, splits or groups on the pod name dimension.
2. If you use aggregate pod counts, no action is required.
3. If you use the pod name dimension, update dashboards, alerts, workbooks, and automation before the retirement date.
4. For pod-level monitoring and troubleshooting, Microsoft recommends Azure Monitor Managed Prometheus and Kubernetes-native pod metrics.