hostmetrics cpu.load.average uses wrong unit #29914
Assignees
Labels
Comments
povilasv
added
bug
songy23
added
receiver/hostmetrics
and removed
needs triage
|
Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
dmitryax
pushed a commit
that referenced
this issue
Jan 5, 2024
**Description:** The system.cpu.load_average.5m uses 1 as unit, which is reserved for utilization metrics - https://opentelemetry.io/docs/specs/semconv/general/metrics/#instrument-units CPU Load Average does not track utilization and can go above **Link to tracking Issue:** #29914
cparkins
pushed a commit
to AmadeusITGroup/opentelemetry-collector-contrib
that referenced
this issue
Jan 10, 2024
) **Description:** The system.cpu.load_average.5m uses 1 as unit, which is reserved for utilization metrics - https://opentelemetry.io/docs/specs/semconv/general/metrics/#instrument-units CPU Load Average does not track utilization and can go above **Link to tracking Issue:** open-telemetry#29914
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/hostmetrics
What happened?
Description
The system.cpu.load_average.5m uses 1 as unit, which is reserved for utilization metrics - https://opentelemetry.io/docs/specs/semconv/general/metrics/#instrument-units
CPU Load Average does not track utilization and can go above 1
Steps to Reproduce
Expected Result
Actual Result
Collector version
v0.91.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: