-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add a metric to report container lifecycle phase (e.g. k8s.container.phase
)
#34406
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This will need to be added as a Semantic Convention as well but looks quite similar to the situation's of open-telemetry/semantic-conventions#1181 |
This change also bring back the age old issue with how do we actually do enums :/ Ref #24425 |
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 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. |
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
k8s.pod.phase
allows to report the pod phase in its lifecycle, however it does not give enough information to report the phase of each container when the pod has more than 1 container running. An additional metric should be available to report the phase for each containerDescribe the solution you'd like
Implement either
k8s.container.phase
ink8sclusterreceiver
or add a resource attributek8s.container.phase
intarget_info
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: