You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Basmajian, Raffi" <rb...@ofiglobal.com> on 2015/11/02 05:35:51 UTC
Critical metrics to monitor over JMX?
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.
Re: Critical metrics to monitor over JMX?
Posted by Tim Bain <tb...@alumni.duke.edu>.
The thing I'm generally most concerned about is whether messages are
backing up on queues or in topic subscriptions, since that usually means a
performance problem somewhere in the system. So that plus JB's suggestion
of monitoring how usage compares to the various broker/store limits would
be what I'd focus on.
On Nov 2, 2015 7:16 AM, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
> This is the Decanter Kibana ActiveMQ dashboard:
>
>
> https://github.com/apache/karaf-decanter/blob/master/kibana/src/main/resources/app/dashboards/activemq.json
>
> You can see the filters on the JMX attributes.
>
> Regards
> JB
>
> On 11/02/2015 03:08 PM, Basmajian, Raffi wrote:
>
>> Tim,
>> I'm not worried about real-time volume, I'm more concerned about which
>> metrics are important to monitor. We're using an agent on the broker to
>> collect metrics; it's JMX-based and pushes metrics to remote storage.
>> Though I like the jolokia REST interface for ad-hoc/casual use, I don't see
>> it being a practical solution for collection in this case. (unless I'm
>> missing something?)
>>
>> JB,
>> Got a link for this? Karaf Decanter for the ActiveMQ view
>>
>>
>> Raffi
>>
>> -----Original Message-----
>> From: tbain98@gmail.com [mailto:tbain98@gmail.com] On Behalf Of Tim Bain
>> Sent: Monday, November 02, 2015 8:43 AM
>> To: ActiveMQ Users
>> Subject: Re: Critical metrics to monitor over JMX? [ EXTERNAL ]
>>
>> 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é" <jb...@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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Critical metrics to monitor over JMX?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
This is the Decanter Kibana ActiveMQ dashboard:
https://github.com/apache/karaf-decanter/blob/master/kibana/src/main/resources/app/dashboards/activemq.json
You can see the filters on the JMX attributes.
Regards
JB
On 11/02/2015 03:08 PM, Basmajian, Raffi wrote:
> Tim,
> I'm not worried about real-time volume, I'm more concerned about which metrics are important to monitor. We're using an agent on the broker to collect metrics; it's JMX-based and pushes metrics to remote storage. Though I like the jolokia REST interface for ad-hoc/casual use, I don't see it being a practical solution for collection in this case. (unless I'm missing something?)
>
> JB,
> Got a link for this? Karaf Decanter for the ActiveMQ view
>
>
> Raffi
>
> -----Original Message-----
> From: tbain98@gmail.com [mailto:tbain98@gmail.com] On Behalf Of Tim Bain
> Sent: Monday, November 02, 2015 8:43 AM
> To: ActiveMQ Users
> Subject: Re: Critical metrics to monitor over JMX? [ EXTERNAL ]
>
> 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é" <jb...@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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
RE: Critical metrics to monitor over JMX?
Posted by "Basmajian, Raffi" <rb...@ofiglobal.com>.
Tim,
I'm not worried about real-time volume, I'm more concerned about which metrics are important to monitor. We're using an agent on the broker to collect metrics; it's JMX-based and pushes metrics to remote storage. Though I like the jolokia REST interface for ad-hoc/casual use, I don't see it being a practical solution for collection in this case. (unless I'm missing something?)
JB,
Got a link for this? Karaf Decanter for the ActiveMQ view
Raffi
-----Original Message-----
From: tbain98@gmail.com [mailto:tbain98@gmail.com] On Behalf Of Tim Bain
Sent: Monday, November 02, 2015 8:43 AM
To: ActiveMQ Users
Subject: Re: Critical metrics to monitor over JMX? [ EXTERNAL ]
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é" <jb...@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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
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.
Re: Critical metrics to monitor over JMX?
Posted by Tim Bain <tb...@alumni.duke.edu>.
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é" <jb...@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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Critical metrics to monitor over JMX?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com