Fix app.mem_usage (Windows)#21085
Merged
thiagoftsm merged 2 commits intonetdata:masterfrom Oct 2, 2025
Merged
Conversation
github-actions
bot
added
area/collectors
thiagoftsm
changed the title
ilyam8
reviewed
Oct 2, 2025
ilyam8
approved these changes
Oct 2, 2025
Member
ilyam8
left a comment
ilyam8
left a comment
There was a problem hiding this comment.
I think mem_private_usage can be removed on Win after this change
Contributor
Author
|
Hello @ilyam8 , I've just checked the 
This is likely because the |
Member
No, it is not. You didn’t understand my message. |
stelfrag
pushed a commit
to stelfrag/netdata
that referenced
this pull request
Oct 3, 2025
(cherry picked from commit 55f71b4)
Merged
thiagoftsm
added a commit
to thiagoftsm/netdata
that referenced
this pull request
Oct 3, 2025
Ferroin
pushed a commit
that referenced
this pull request
Oct 15, 2025
(cherry picked from commit 55f71b4)
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
2 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.
Summary
The
app.mem_usagevalue on Windows currently has a major discrepancy with the Windows Task Manager due to an incorrect data collection key.This PR fixes the issue by correcting the variable name, bringing the reported value much closer to Task Manager's.
This branch:
Next image shows this PR on left and current master on right:
Test Plan
app.mem_usageselect netdata and compare with Task Manager values.Additional Information
For users: How does this change affect me?