Skip to content
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

Open
epochstamp opened this issue Aug 5, 2024 · 3 comments
Labels

Comments

@epochstamp
Copy link

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 container

Describe the solution you'd like

Implement either k8s.container.phase in k8sclusterreceiver or add a resource attribute k8s.container.phase in target_info

Describe alternatives you've considered

No response

Additional context

No response

@epochstamp epochstamp added enhancement New feature or request needs triage New item requiring triage labels Aug 5, 2024
Copy link
Contributor

github-actions bot commented Aug 5, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@ChrsMark
Copy link
Member

ChrsMark commented Aug 6, 2024

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

@povilasv
Copy link
Contributor

povilasv commented Aug 6, 2024

This change also bring back the age old issue with how do we actually do enums :/ Ref #24425

@Frapschen Frapschen removed the needs triage New item requiring triage label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants