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?
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?
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?
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?
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:
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?
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.