# JMX naming **URL:** \ **Category:** Elasticsearch\ **Created:** [April 8, 2011, 2:27pm UTC](https://discuss.elastic.co/t/jmx-naming/4204 "2011-04-08T14:27:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [April 8, 2011, 2:27pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/1 "2011-04-08T14:27:13Z")
Hi Shay, we're in the last stages of productionising our solution. We are now facing a little issue with the monitoring of our app using JMX. Elasticsearch seems to be adding a random (enough) node id to the name of the ES MBean which changes. This means that we can't currently monitor ES. Is there any way to override this behaviour such that the MBean is exposed with a static (or config derived) name? Thanks, ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 8, 2011, 3:51pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/2 "2011-04-08T15:51:34Z")
I changed it to org.elasticsearch static one. The idea was to have each node a JMX aggregator of other nodes, but gave up on that. Here is the issue: [JMX: Don't use node id and name as part of the jmx registration, use static org.elasticsearch · Issue #843 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/843). As a side note, not a big fan of JMX, very heavy on system resources. The different stats/info/status APIs in elasticsearch gives you a lot of information. Actually, those include, currently, much more info than JMX, so if you miss something, it can be easily added to JMX. -shay.banon On Friday, April 8, 2011 at 5:27 PM, Paul Loy wrote: > Hi Shay, > > we're in the last stages of productionising our solution. We are now facing a little issue with the monitoring of our app using JMX. Elasticsearch seems to be adding a random (enough) node id to the name of the ES MBean which changes. This means that we can't currently monitor ES. > > Is there any way to override this behaviour such that the MBean is exposed with a static (or config derived) name? > > Thanks, > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [April 8, 2011, 3:59pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/3 "2011-04-08T15:59:01Z")
Cool, thanks! Yeah I don't like JMX much either, but it's what our support teams use so if I don't want to provide 24/7 support I have to expose things in JMX ☹ Cheers, Paul. On Fri, Apr 8, 2011 at 4:51 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > I changed it to org.elasticsearch static one. The idea was to have each > node a JMX aggregator of other nodes, but gave up on that. Here is the > issue: [JMX: Don't use node id and name as part of the jmx registration, use static org.elasticsearch · Issue #843 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/843). > > As a side note, not a big fan of JMX, very heavy on system resources. The > different stats/info/status APIs in elasticsearch gives you a lot of > information. > > Actually, those include, currently, much more info than JMX, so if you miss > something, it can be easily added to JMX. > > -shay.banon > > On Friday, April 8, 2011 at 5:27 PM, Paul Loy wrote: > > Hi Shay, > > we're in the last stages of productionising our solution. We are now facing > a little issue with the monitoring of our app using JMX. Elasticsearch seems > to be adding a random (enough) node id to the name of the ES MBean which > changes. This means that we can't currently monitor ES. > > Is there any way to override this behaviour such that the MBean is exposed > with a static (or config derived) name? > > Thanks, > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![dpilato](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpilato/32/2449_2.png) [@dpilato](https://discuss.elastic.co/u/dpilato)\ **Post date:** [April 8, 2011, 4:04pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/4 "2011-04-08T16:04:52Z")
Hi, [http://www.elasticsearch.org/guide/reference/modules/jmx.html](http://www.elasticsearch.org/guide/reference/modules/jmx.html) says that : jmx.domain The domain under which the JMX will register under can be set using jmx.domain setting. It defaults to {elasticsearch}. Perhaps, you could try to set jmx.domain property ? When I start a JMX connection, I get : It seems to be correct Hope this helps De : Paul Loy [[mailto:keteracel@gmail.com](mailto:keteracel@gmail.com)] Envoyé : vendredi 8 avril 2011 16:27 À : [users@elasticsearch.com](mailto:users@elasticsearch.com) Objet : JMX naming Hi Shay, we're in the last stages of productionising our solution. We are now facing a little issue with the monitoring of our app using JMX. Elasticsearch seems to be adding a random (enough) node id to the name of the ES MBean which changes. This means that we can't currently monitor ES. Is there any way to override this behaviour such that the MBean is exposed with a static (or config derived) name? Thanks, ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 8, 2011, 4:06pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/5 "2011-04-08T16:06:04Z")
Yes, but then you will still have the node id/name as a second level element, which is no longer the case. On Friday, April 8, 2011 at 7:04 PM, David Pilato wrote: > Hi, > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/jmx.html) says that : > jmx.domain > The domain under which the JMX will register under can be set using jmx.domain setting. It defaults to {elasticsearch}. > > Perhaps, you could try to set jmx.domain property ? > > When I start a JMX connection, I get : > > It seems to be correct… > > Hope this helps > > De : Paul Loy [[mailto:keteracel@gmail.com](mailto:keteracel@gmail.com)] > Envoyé : vendredi 8 avril 2011 16:27 > À : [users@elasticsearch.com](mailto:users@elasticsearch.com) > Objet : JMX naming > > Hi Shay, > > we're in the last stages of productionising our solution. We are now facing a little issue with the monitoring of our app using JMX. Elasticsearch seems to be adding a random (enough) node id to the name of the ES MBean which changes. This means that we can't currently monitor ES. > > Is there any way to override this behaviour such that the MBean is exposed with a static (or config derived) name? > > Thanks, > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![dpilato](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpilato/32/2449_2.png) [@dpilato](https://discuss.elastic.co/u/dpilato)\ **Post date:** [April 8, 2011, 4:06pm UTC](https://discuss.elastic.co/t/jmx-naming/4204/6 "2011-04-08T16:06:38Z")
Sorry I answer a bit late ! 😉 BTW I saw that someone wrote nagios plugins to monitor ES . It could help you David. De : David Pilato [[mailto:david.pilato@douane.finances.gouv.fr](mailto:david.pilato@douane.finances.gouv.fr)] Envoyé : vendredi 8 avril 2011 18:05 À : [users@elasticsearch.com](mailto:users@elasticsearch.com) Objet : RE: JMX naming Hi, [http://www.elasticsearch.org/guide/reference/modules/jmx.html](http://www.elasticsearch.org/guide/reference/modules/jmx.html) says that : jmx.domain The domain under which the JMX will register under can be set using jmx.domain setting. It defaults to {elasticsearch}. Perhaps, you could try to set jmx.domain property ? When I start a JMX connection, I get : It seems to be correct Hope this helps De : Paul Loy [[mailto:keteracel@gmail.com](mailto:keteracel@gmail.com)] Envoyé : vendredi 8 avril 2011 16:27 À : [users@elasticsearch.com](mailto:users@elasticsearch.com) Objet : JMX naming Hi Shay, we're in the last stages of productionising our solution. We are now facing a little issue with the monitoring of our app using JMX. Elasticsearch seems to be adding a random (enough) node id to the name of the ES MBean which changes. This means that we can't currently monitor ES. Is there any way to override this behaviour such that the MBean is exposed with a static (or config derived) name? Thanks, ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**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, 4:08am UTC](https://discuss.elastic.co/t/jmx-naming/4204/7 "2017-07-06T04:08:42Z")