-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[k8scluster] add k8s.container.status_waiting_reason metric #32457
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
FYI I've opened a PR on semconv for last terminated reason -> open-telemetry/semantic-conventions#922 and looks like some refactorings are needed on my PR. So this time let's first agree if we want this and then make a PR to semconv |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I am seeing that the I am happy to contribute, if required. |
FYI this was reverted in open-telemetry/semantic-conventions#1115 see the discussion in original PR open-telemetry/semantic-conventions#997 |
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
I would like to get some container state metrics, about waiting reason. One use case is to know whether the container is in CrashLoopBackOff.
Example happening in pod:
Kube State Metrics has this modelled as this Prometheus metric:
Ref: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/workload/pod-metrics.md
So would be great to have a similar metric.
Describe the solution you'd like
https://github.com/kubernetes/kube-state-metrics/blob/main/internal/store/pod.go#L554-L578
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: