You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some metrics, such as container.memory.page_faults, use 1 for Unit, but should be changed to use the appropriate Unit according to Metrics Semantic Conventions.
For example, when using the Prometheus Exporter, metrics in OpenTelemetry format are normalized to metric names according to conventions in Prometheus by looking at Unit, Metric Type, etc.
walnuts1018
changed the title
Unit 1 must be used only for fractions and ratios
[receiver/kubeletstats] Unit 1 must be used only for fractions and ratios
Oct 17, 2024
Component(s)
receiver/kubeletstats
Describe the issue you're reporting
Describe
Some metrics, such as
container.memory.page_faults
, use1
for Unit, but should be changed to use the appropriate Unit according to Metrics Semantic Conventions.Metrics that need to be modified
container.memory.major_page_faults
1
to{page_fault}
.container.memory.page_faults
1
to{page_fault}
.k8s.node.memory.major_page_faults
1
to{page_fault}
.k8s.node.memory.page_faults
1
to{page_fault}
.k8s.pod.memory.major_page_faults
1
to{page_fault}
.k8s.pod.memory.page_faults
1
to{page_fault}
.k8s.volume.inodes
1
to{inode}
.k8s.volume.inodes.free
1
to{inode}
.k8s.volume.inodes.used
1
to{inode}
.Problems caused by using 1 for Unit
For example, when using the Prometheus Exporter, metrics in OpenTelemetry format are normalized to metric names according to conventions in Prometheus by looking at Unit, Metric Type, etc.
If a metric has a
Metric Type
ofGauge
and aUnit
of1
, the Prometheus Translator will assume that the metric represents a percentage of 0-1 and assign a Suffix of_ratio
(https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/translator/prometheus#:~:text=Percentages%20(unit%20is%201)), which is highly misleading. This is highly misleading.The text was updated successfully, but these errors were encountered: