-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding more labels to kube_pod_status_phase #332
Comments
I will be more than happy to open a PR if we agree that this is a reasonable ask. |
That can be done at query time. Prometheus supports joins, so you can join pod info on the phase to figure out the node. |
Close this via @brancz's comments above. In case you have not used the join syntax of Prometheus, there is an example in the #137 comment with some query like:
|
thank you very much guys. I will try this out tonight |
we had a situation where # of failed pod counts increased dramatically, and we were wondering what happened.
on debugging we found 2 nodes were having docker issues and most of the failed nodes were being scheduled on those problematic nodes.
i think it will be useful to add more labels to kube_pod_status_phase, so that we can run query like all failed pods count group by node.
The text was updated successfully, but these errors were encountered: