You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Elasticsearch v1.4.4 and I like this plugin. I recognized that the "jvm_stats max_heap_size_in_bytes" has been already done by ES. The "heap_max_in_bytes" has the same value.
node['jvm']['mem']['heap_max_in_bytes']
And one more, adding "used_in_bytes" for each pool is also useful, so we can see how GC work in real time, we can see the "GC frequency and duration" as from ES official guide . I had patched it for myself.
node['jvm']['mem']['pools'].each do |k, v|
# get `used_in_bytes`.
metrics["jvm.mem.#{k.tr(' ', '_')}.used_in_bytes"] = v['used_in_bytes']
metrics["jvm.mem.#{k.tr(' ', '_')}.max_in_bytes"] = v['max_in_bytes']
The text was updated successfully, but these errors were encountered:
chrisduong
changed the title
[metric-es-node-graphite] jvm_stats max_heap_size_in_bytes already done by Elasticsearch
[metrics-es-node-graphite] jvm_stats max_heap_size_in_bytes already done by Elasticsearch
May 18, 2016
Hi,
I'm using Elasticsearch v1.4.4 and I like this plugin. I recognized that the "jvm_stats max_heap_size_in_bytes" has been already done by ES. The "heap_max_in_bytes" has the same value.
And one more, adding "used_in_bytes" for each pool is also useful, so we can see how GC work in real time, we can see the "GC frequency and duration" as from ES official guide . I had patched it for myself.
The text was updated successfully, but these errors were encountered: