# Jmx river **URL:** \ **Category:** Elasticsearch\ **Created:** [November 23, 2012, 4:11pm UTC](https://discuss.elastic.co/t/jmx-river/9806 "2012-11-23T16:11:56Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![clandestino\_bgd\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clandestino_bgd_2/32/1315_2.png) [@clandestino\_bgd\_2](https://discuss.elastic.co/u/clandestino_bgd_2)\ **Post date:** [November 23, 2012, 4:11pm UTC](https://discuss.elastic.co/t/jmx-river/9806/1 "2012-11-23T16:11:56Z")
Hi all, I am thinking about the general monitoring app which would parse logs and periodically read jmx metrics exposed in my spring based app. for logs, I am planning to use logstash which comes with ES as a datastore. Having something that polls my JMX metrics / mbean attributes and publish them in ES index with the timestamp sounds tempting, since then I can build thin JS client to display aggregated log and JMX views. Did anybody think about creating jmx river? Does somebody see anything wrong about that? Is there any recommendation / idea already? Thanks very much for ES and the great work on this mailing list? Milan -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:03am UTC](https://discuss.elastic.co/t/jmx-river/9806/2 "2017-07-06T03:03:08Z")