# Jmx input: undefined method 'event' **URL:** \ **Category:** Logstash\ **Created:** [January 3, 2017, 2:40pm UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442 "2017-01-03T14:40:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![frankkoornstra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankkoornstra/32/6780_2.png) [@frankkoornstra](https://discuss.elastic.co/u/frankkoornstra)\ **Post date:** [January 3, 2017, 2:40pm UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/1 "2017-01-03T14:40:54Z")
I'm trying to use the jmx input for Logstash (2.4.0) but get the following error: `{:timestamp=>"2017-01-03T14:28:13.344000+0000", :message=>"undefined method 'event' for #", :level=>:warn}` It seems to be explained in this comment: [https://github.com/logstash-plugins/logstash-input-jmx/issues/26#issuecomment-257024957](https://github.com/logstash-plugins/logstash-input-jmx/issues/26#issuecomment-257024957). My question is: how does this work? Does the plugin maintainer have to create a new build which Elastic then accepts, can he/she publish the new build him/her self, can we update this plugin ourselves? And if it's the former two, how do I get the ball rolling on that one? Thanks! 🙂 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 5, 2017, 1:14am UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/2 "2017-01-05T01:14:06Z")
Feel free to raise a PR and then post back in here to make the team aware 🙂 ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 8, 2017, 4:08pm UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/3 "2017-01-08T16:08:35Z")
@warkolm, there is a PR since almost two months back. > @frankkoornstra, keep in mind that one available option is to build a gem yourself and install it with the usual logstash-plugin command. While it's certainly more convenient to wait for an officially released gem you're never stranded. ---
**Author:** ![frankkoornstra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankkoornstra/32/6780_2.png) [@frankkoornstra](https://discuss.elastic.co/u/frankkoornstra)\ **Post date:** [January 9, 2017, 10:53am UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/4 "2017-01-09T10:53:51Z")
Ok, nice to know that that is an option. It would be good though that the default install of a, what seems to me as essential plugin, is not broken. Besides, it took quite some googling and issue browsing (although hopefully less now that this topic is here) to find out why. I was hoping that the maintainers were maybe here as well or at least someone that knows a girl that knows a guy that knows the maintainer 🙂 ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 9, 2017, 10:55am UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/5 "2017-01-09T10:55:33Z")
Judging by its [CONTRIBUTORS file](https://github.com/logstash-plugins/logstash-input-jmx/blob/master/CONTRIBUTORS) the plugin doesn't _have_ a maintainer. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 6, 2017, 10:55am UTC](https://discuss.elastic.co/t/jmx-input-undefined-method-event/70442/6 "2017-02-06T10:55:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.