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
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.
The text was updated successfully, but these errors were encountered:
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?
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:
We've looked at the Elastic Metrics, but it seems it doesn't gather data from inside a JVM, only from the host OS.
The text was updated successfully, but these errors were encountered: