Keep in mind that JMX is slow and you're not going to get thousands of metric values per second. My experience was somewhere around 50 to 100 per second, though your mileage may vary. If you're worried that may not be enough, the Jolokia REST interface is supposed to be much faster. On Nov 2, 2015 5:01 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net> wrote:
> Hi Raffi, > > I would monitor: > - the JVM standard (threads, memory, etc) > - the system usage percent usage (broker object name) > - the pending messages (destination object names) > > It's what we described by default in Karaf Decanter for the ActiveMQ view. > > Regards > JB > > On 11/02/2015 05:35 AM, Basmajian, Raffi wrote: > >> Aside from the obvious metrics such as cpu, heap, active connections, >> producer/consumer count, and persistent store usage, are there any subtle >> metrics to monitor over JMX for maintaining complete operational coverage >> of this product? >> >> Is there a limit to the number of threads, connections, or sessions a >> broker creates? If so, where are these limits defined? >> >> Raffi >> >> >> >> >> >> This e-mail transmission may contain information that is proprietary, >> privileged and/or confidential and is intended exclusively for the >> person(s) to whom it is addressed. Any use, copying, retention or >> disclosure by any person other than the intended recipient or the intended >> recipient's designees is strictly prohibited. If you are not the intended >> recipient or their designee, please notify the sender immediately by return >> e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, >> monitor, review, retain and/or disclose the content of all email >> communications. >> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
