Remove ram.percent from CAT Node default columns #108465
Open
+6
−1
Conversation
This file contains 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
👋 @dakrone as follow-up to #32393 closing, could we consider a smaller win to reduce the symptom surface area of removing `ram.percent` from the default columns of [CAT Nodes](https://www.elastic.co/guide/en/elasticsearch/reference/master/cat-nodes.html)? Support (at least) encourages users to ignore it entirely and focus on `heap.percent` (which already is default).
stefnestor
added
>enhancement
:Data Management/Stats
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine
added
external-contributor
|
Hi @stefnestor, I've created a changelog YAML for you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
👋 @dakrone as follow-up to your closing #32393 yesterday, could we consider a smaller win to reduce the symptom surface area of removing
ram.percentfrom the default columns of CAT Nodes? Support (at least) encourages users to ignore it entirely and focus onheap.percent(which already is default).