Cherry-pick #17268 to 7.x: Update documentation for system.process.memory fields to include clarification on Windows memory terminology #17287
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.
Cherry-pick of PR #17268 to 7.x branch. Original message:
What does this PR do?
Updates the description of the system/process memory fields.
Why is it important?
Related to #8345
Windows users are confused about the values reflected in the
system.process.memory.rss.bytes
andsystem.process.memory.size
since the description and naming are not clear enough on the type of memory used/allocated etc.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues