We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I feel like this is a stupid question; How can I create Prometheus rules from this, and make this useful for my environment?
Can you add something like to the README in an ELI5 fashion?
Viele danke.
The text was updated successfully, but these errors were encountered:
you could use an alert definition like this one to alert on OOM killed pods:
alert: ComponentOutOfMemory expr: sum_over_time(kube_pod_container_status_terminated_reason{reason="OOMKilled"}[5m]) > 0 for: 10s labels: severity: warning annotations: description: Critical Pod {{$labels.namespace}}/{{$labels.pod}} was OOMKilled.
Sorry, something went wrong.
For completeness: kube_pod_container_status_terminated_reason is provided by /~https://github.com/kubernetes/kube-state-metrics.
kube_pod_container_status_terminated_reason
Please have a look at kubernetes/kube-state-metrics#535.
kube_pod_container_status_last_terminated_reason (notice the last part) seems like the better metric to use.
kube_pod_container_status_last_terminated_reason
last
No branches or pull requests
Hi,
I feel like this is a stupid question; How can I create Prometheus rules from this, and make this useful for my environment?
Can you add something like to the README in an ELI5 fashion?
Viele danke.
The text was updated successfully, but these errors were encountered: