New metric kubernetes.container.status_waiting_reason for kubernetes.state_container datastream of K8s integration

[gizas]

Context

As part of the investigation of #7994 ,we have identified that the relevent Status error that is depicted in Status column of kubectl output is not available in our K8s Observability collection.

k get pods -n default
NAME                                      READY   STATUS             RESTARTS        AGE
nginx-787c9d6bc4-s9sxp   1/2     CrashLoopBackOff   369 (69s ago)   21h

So the STATUS= CrashLoopBackOff is not available in any metric of our k8s integration.

We believe that this new metric can enhance the UX of our users and help them to troubleshoot pod and container problems in their cluster

Goal
We suggest to introduce a new metric called kubernetes.container.status_waiting_reason in datastream kubernetes.state_container that will make use of kube_pod_container_status_waiting_reason from kube pod-metrics.md

This metrics is in Stable status

Deliverables

• Beats code that will introduce this new metrics in k8s module
• New version of K8s Integration with this new field kubernetes.container.status_waiting_reason available
• Documentation updates for relevant changes

[gizas]

Field is there under kubernetes.container.status.reason:

Closing this