JMX naming


(Paul Loy) #1

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
http://uk.linkedin.com/in/paulloy


(Shay Banon) #2

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: 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
http://uk.linkedin.com/in/paulloy


(Paul Loy) #3

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 :frowning:

Cheers,

Paul.

On Fri, Apr 8, 2011 at 4:51 PM, Shay Banon shay.banon@elasticsearch.comwrote:

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: 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
http://uk.linkedin.com/in/paulloy

--

Paul Loy
paul@keteracel.com
http://uk.linkedin.com/in/paulloy


(dpilato) #4

Hi,

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]
Envoyé : vendredi 8 avril 2011 16:27
À : 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
http://uk.linkedin.com/in/paulloy


(Shay Banon) #5

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,

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]
Envoyé : vendredi 8 avril 2011 16:27
À : 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
http://uk.linkedin.com/in/paulloy


(dpilato) #6

Sorry
I answer a bit late ! :wink:

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]
Envoyé : vendredi 8 avril 2011 18:05
À : users@elasticsearch.com
Objet : RE: JMX naming

Hi,

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]
Envoyé : vendredi 8 avril 2011 16:27
À : 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
http://uk.linkedin.com/in/paulloy


(system) #7