-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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/hostmetricsreceiver] Gopsutil error on windows with multiple processor groups. #33340
Labels
Comments
alvarocabanas
added
bug
Something isn't working
needs triage
New item requiring triage
labels
Jun 3, 2024
Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Jun 5, 2024
This was referenced Jun 19, 2024
This was referenced Jul 16, 2024
This was referenced Jul 30, 2024
This was referenced Aug 13, 2024
This was referenced Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
receiver/hostmetricsreceiver
What happened?
Description
On a windows instance having 48 * 2 logical cpus, windows groups CPUs into batches of 64 logical cpus in a processor group, but Gopsutil's Cpu.TimesWitContext defined on the cpuscraper in here and used to by the resource detector to calculate the cpu times and utilization, indistinctly gets this data from one of the two processor groups and not all of them.
This is generating variable cpu Utilization, sometimes negative and sometimes full usage even if only half the cores are running.
This bug is reported on the gopsutil library.
Steps to Reproduce
In our case we reproduced it on a 'm5n.metal' machine in AWS with windows-server-22 but we know reports of it happening in other windows with more than one processor groups.
Expected Result
Correct Cpu Usage and times.
Actual Result
Cpu data points from one of the 2 processor groups randomly.
Collector version
v0.101.0
Environment information
Environment
OS: Windows-server 22
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: