Skip to content
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

[metrics-es-node-graphite] jvm_stats max_heap_size_in_bytes already done by Elasticsearch #40

Open
chrisduong opened this issue May 18, 2016 · 1 comment

Comments

@chrisduong
Copy link

chrisduong commented 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.

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']
@chrisduong 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
@majormoses
Copy link
Member

@chrisduong sounds like something we want, do you have a pr for review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants