-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/K8scluster] Add additional attributes to the k8s.container.restarts metric #31418
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I like this attribute. |
I will try and raise a draft PR |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
Currently, the
k8s.container.restarts
metric does not include the metadata such as the reason for the restart and the exit codeDescribe the solution you'd like
Add
terminated_reason
andexit_code
attributes to thek8s.container.restarts
metrics where appropriateDescribe alternatives you've considered
The current alternative is to use the Kube State Metrics's
kube_pod_container_status_terminated_reason
andkube_pod_container_status_last_terminated_exitcode
metricsAdditional context
A related metric issue has been raised: #31282 (comment)
The text was updated successfully, but these errors were encountered: