You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 code
Describe the solution you'd like
Add terminated_reason and exit_code attributes to the k8s.container.restarts metrics where appropriate
Describe alternatives you've considered
The current alternative is to use the Kube State Metrics's kube_pod_container_status_terminated_reason and kube_pod_container_status_last_terminated_exitcode metrics
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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
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: