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.

Sign up for GitHub

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

Jump to bottom

[k8s] Define semantic conventions for k8s network metrics #1487

Open
ChrsMark opened this issue Oct 17, 2024 · 0 comments · May be fixed by #1427
Open

[k8s] Define semantic conventions for k8s network metrics #1487

ChrsMark opened this issue Oct 17, 2024 · 0 comments · May be fixed by #1427
Assignees
@AlexanderWert
Labels
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

Comments

@ChrsMark
Copy link
Member

Area(s)

No response

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

As part of the K8s SemConv stability work we need to define k8s network 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.node.network.io
k8s.node.network.errors
k8s.pod.network.io
k8s.pod.network.errors

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
This was referenced Oct 17, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexanderWert AlexanderWert

Labels
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add k8s.{pod,node}.network.{io,errors} metrics ChrsMark/semantic-conventions
2 participants
@AlexanderWert @ChrsMark