Remove "Accurate CPU counts not available on platform" log spam on MacOS at the debug level#266
Merged
cmacknz merged 2 commits intoelastic:mainfrom Oct 14, 2025
Merged
Conversation
mauri870
approved these changes
Oct 13, 2025
Member
mauri870
left a comment
There was a problem hiding this comment.
Approving, pending Pierre's comment.
pierrehilbert
approved these changes
Oct 14, 2025
This was referenced Oct 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See elastic/beats#47054. The removed debug log generated 10s to 100s of lines of log spam in Metricbeat and Elastic Agent logs at the debug level on my MacOS machine. We can see that
numCPUisn't implemented on a platform by inspection in the code, we don't need a log for it.Also for some reason the notice file was out of date, so that is updated too.