# Topbeat for JVM metrics monitoring **URL:** https://discuss.elastic.co/t/topbeat-for-jvm-metrics-monitoring/38444 **Category:** Beats **Created:** [January 5, 2016, 10:40pm UTC](https://discuss.elastic.co/t/topbeat-for-jvm-metrics-monitoring/38444 "2016-01-05T22:40:53Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh) #### Post date: [January 5, 2016, 11:28pm UTC](https://discuss.elastic.co/t/topbeat-for-jvm-metrics-monitoring/38444/2 "2016-01-05T23:28:52Z")
No, it cannot. There is no Beat for JVM monitoring at the current time. This was discuss a bit here: > [@Beat to feed JMX data of Java processes to ES](https://discuss.elastic.co/t/beat-to-feed-jmx-data-of-java-processes-to-es/34465/3): > > Was busy with testing RC2, nightly builds recently and can now come back to this question... I was inspired by the nginx beat which uses the same approach to pull the information. Maybe it's more an architecture decision. IMHO, well defined monitoring interfaces to pull information like http, jmx should be handled by a beat implementation itself. Then you can avoid an additional daemon running on the system which feeds the data into your proposed generic beat with an http input. Thanks Oli --- _[View the full topic](https://discuss.elastic.co/t/topbeat-for-jvm-metrics-monitoring/38444)._