-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[metricbeat:elasticsearch module] Missing jvm.mem.pools metrics from node.stats #40539
Labels
Team:Monitoring
Stack Monitoring team
Comments
przemek-grzedzielski
changed the title
[elasticsearch module] Missing jvm.mem.pools metrics from node.stats
[metricbeat:elasticsearch module] Missing jvm.mem.pools metrics from node.stats
Aug 15, 2024
@przemek-grzedzielski The actual PR where the My hunch is that those fields have been removed because they were nowhere used in the Stack Monitoring UI, which looking at the SM UI source code seems to confirm this. Maybe @pickypg has an idea or some background context since he was involved at that time. |
4 tasks
Merged
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found that metricbeat v 8.13.4 is not ingesting some of the
elasticsearch.node.stats.jvm.mem.*
metrics, in particular:elasticsearch.node.stats.jvm.mem.pools.old.max.bytes
andelasticsearch.node.stats.jvm.mem.pools.old.used.bytes
.Note that these (and other missing metrics) are listed in the Metricbeat 8.x documentation. They're also present in the mappings:
beats/metricbeat/module/elasticsearch/node_stats/_meta/fields.yml
Line 179 in 46fd21c
beats/metricbeat/module/elasticsearch/node_stats/_meta/fields.yml
Line 164 in 46fd21c
They're also exposed via Elasticsearch APIs as per the node_stats API documentation (also tested that this is the case).
@nkvoll traced the changes back to this commit or this Pull Request.
It seems that these fields have been removed inadvertently and the ask is that they be brought back since a number of services depend on them.
For confirmed bugs, please report:
The text was updated successfully, but these errors were encountered: