Description
Metrics on Windows report values in the [0,100] range despite the documentation mentioning the [0,1] range:
https://learn.microsoft.com/en-us/dotnet/core/diagnostics/built-in-metrics-diagnostics#metric-containercpulimitutilization
For example, if container CPU limit utilization is 60%, the metric reports the 60 value instead of 0.6.
Affected metrics:
dotnet.process.memory.virtual.utilizationprocess.cpu.utilizationcontainer.memory.limit.utilizationcontainer.cpu.limit.utilization
Reproduction Steps
Just use Resource Monitoring library on Windows and an exporter for the affected metrics, and you will see the incorrect values.
Expected behavior
Metrics on Windows report values in the [0,1] range as documented. For example, if container CPU limit utilization is 60%, the metric should report the 0.6 value
Actual behavior
Metrics on Windows report values in the [0,100] range. For example, if container CPU limit utilization is 60%, the metric reports the 60 value
Regression?
No, it behaves like that since the introduction in #5290
Known Workarounds
No response
Configuration
No response
Other information
No response
Description
Metrics on Windows report values in the [0,100] range despite the documentation mentioning the [0,1] range:
https://learn.microsoft.com/en-us/dotnet/core/diagnostics/built-in-metrics-diagnostics#metric-containercpulimitutilization
For example, if container CPU limit utilization is 60%, the metric reports the
60value instead of0.6.Affected metrics:
dotnet.process.memory.virtual.utilizationprocess.cpu.utilizationcontainer.memory.limit.utilizationcontainer.cpu.limit.utilizationReproduction Steps
Just use Resource Monitoring library on Windows and an exporter for the affected metrics, and you will see the incorrect values.
Expected behavior
Metrics on Windows report values in the [0,1] range as documented. For example, if container CPU limit utilization is 60%, the metric should report the
0.6valueActual behavior
Metrics on Windows report values in the [0,100] range. For example, if container CPU limit utilization is 60%, the metric reports the
60valueRegression?
No, it behaves like that since the introduction in #5290
Known Workarounds
No response
Configuration
No response
Other information
No response