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

[k8s] Define semantic conventions for k8s volume metrics #1485

Open
ChrsMark opened this issue Oct 17, 2024 · 1 comment
Open

[k8s] Define semantic conventions for k8s volume metrics #1485

ChrsMark opened this issue Oct 17, 2024 · 1 comment
Labels
area:k8s enhancement New feature or request

Comments

@ChrsMark
Copy link
Member

Area(s)

area:k8s

Is your change request related to a problem? Please describe.

As part of the K8s SemConv stability work we need to define k8s volume metrics that are already in use by the Opentelemetry Collector.

Related to #1032.

Describe the solution you'd like

The existing metrics in use that we need to define as semantic conventions are the following:

k8s.volume.available
k8s.volume.capacity
k8s.volume.inodes
k8s.volume.inodes.free
k8s.volume.inodes.used 

Describe alternatives you've considered

No response

Additional context

No response

@ChrsMark ChrsMark added enhancement New feature or request experts needed This issue or pull request is outside an area where general approvers feel they can approve triage:needs-triage labels Oct 17, 2024
@ChrsMark
Copy link
Member Author

Also related to this one: open-telemetry/opentelemetry-collector-contrib#35849

@joaopgrassi joaopgrassi removed experts needed This issue or pull request is outside an area where general approvers feel they can approve triage:needs-triage labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:k8s enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

3 participants