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

JVM performance counters monitoring #322

Closed
mdindoffer opened this issue Nov 20, 2018 · 3 comments
Closed

JVM performance counters monitoring #322

mdindoffer opened this issue Nov 20, 2018 · 3 comments
Labels
duplicate This issue or pull request already exists

Comments

@mdindoffer
Copy link
Contributor

mdindoffer commented Nov 20, 2018

A vital part of any Java APM is JVM performance reporting. The Elastic Java agent in its current state does not gather JVM performance data. We have to monitor things like Heap usage, GC pauses, etc. using a separate JMX solution.

It would be great if the Java APM could gather all the traditional JVM metrics:

  • GC stats (pauses, generations)
  • Heap, Permgen, Metaspace usage
  • Thread counts (daemon, normal)
  • Classloader stats

We've looked at the Elastic Metrics, but it seems it doesn't gather data from inside a JVM, only from the host OS.

@felixbarny
Copy link
Member

Hi and thanks for your input. This is something we will be working on in the near future.

Closing as duplicate of #112

@felixbarny felixbarny added the duplicate This issue or pull request already exists label Nov 20, 2018
@felixbarny
Copy link
Member

In the meantime, this blog may be relevant to you: https://www.elastic.co/blog/monitoring-java-applications-with-metricbeat-and-jolokia

@mdindoffer
Copy link
Contributor Author

Thanks for the link, we will look into the jolokia solution. But afaik it involves creating our own field-jmx mappings and dashboards, which isn't really appealing.
Is there any rough ETA for the JVM metrics? Can we expect GA in say a couple of months?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants