[Stack Monitoring] Put elasticsearch.node.stats.jvm.mem.pools.*
#40571
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
This re-adds the pools to the `node_stats` metric set.
pickypg
added
bug
backport-8.15
botelastic
bot
added
the
needs_team
botelastic
bot
removed
the
needs_team
|
This pull request is now in conflicts. Could you fix it? 🙏 |
przemek-grzedzielski
approved these changes
Aug 22, 2024
Merged
4 tasks
pickypg
added a commit
that referenced
this pull request
Aug 22, 2024
…ats.jvm.mem.pools.*` (#40590) This re-adds the pools to the `node_stats` metric set. (cherry picked from commit 9146875) --------- Co-authored-by: Chris Earle <[email protected]>
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.
This re-adds the
poolsto thenode_statsmetric set.Proposed commit message
Adds the
elasticsearch.node.stats.jvm.mem.pools.*fields to themetricsetfornode_statsbecause it was removed by accident in a previous release.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
No. The mappings have continued to exist.
Author's Checklist
node_statsmetricsetHow to test this PR locally
Configure Metricbeat:
Connect to Elasticsearch and observe the data stream provides
Without this change, this does not exist in the resulting
_source. With this change, you should see something along the lines of{ "hits" : { "hits" : [ { "_source" : { "elasticsearch" : { "node" : { "stats" : { "jvm" : { "mem" : { "pools" : { "survivor" : { "peak" : { "bytes" : 74424848 }, "peak_max" : { "bytes" : 0 }, "used" : { "bytes" : 12582912 }, "max" : { "bytes" : 0 } }, "old" : { "used" : { "bytes" : 90397592 }, "max" : { "bytes" : 1073741824 }, "peak" : { "bytes" : 91899520 }, "peak_max" : { "bytes" : 1073741824 } }, "young" : { "peak" : { "bytes" : 624951296 }, "peak_max" : { "bytes" : 0 }, "used" : { "bytes" : 293601280 }, "max" : { "bytes" : 0 } } } } } } } } } } ] } }Related issues
Closes #40539
Use cases
Understand the different memory pools in the JVM.