-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/{dockerstatsreceiver, kubeletstatsreceiver}] Collision with metric container.cpu.utilization #24008
Comments
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. |
Links to duplicate named 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 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. |
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 closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/dockerstats, receiver/kubeletstats
Describe the issue you're reporting
Both
dockerstatsreceiver
andkubeletstatsreceiver
emit metric with same namecontainer.cpu.utilization
.In
dockerstatsreceiver
the metric is pulled from: https://pkg.go.dev/github.com/docker/docker@v24.0.2+incompatible/api/types#CPUUsage.PercpuUsageIn
kubeletstatsreceiver
the metric is pulled from:https://pkg.go.dev/k8s.io/kubelet@v0.27.3/pkg/apis/stats/v1alpha1#CPUStats.UsageNanoCores
I believe one should be renamed to avoid the collision.
The text was updated successfully, but these errors were encountered: