Hey Andrea. Thanks for the reply. I will definitely check them out. Does QMAN have any UI to go along with it too?
Thanks gs On Mon, Feb 23, 2009 at 11:52 PM, Andrea Gazzarini <[email protected]>wrote: > Hi, > You could also monitor an instance property or statistics using QMan. > > In fact, QMan is exposing the broker management domain as a set of MBeans. > Each time an MBean instance (i,e, a connection, a queue, etc...) is created > a notification is sent to registered listeners. > So: > - You can register your listener in order to be notified when an instance > of > (for example) connection is created; > - After that you can install a JMX monitor (string, gauge, counter monitor) > in order to watch an attribute of that instance; The monitor will notify > you > when the value changes according to monitor rules. > - If the default monitors shipped with JMX standard API is not enough you > can write a new one. > > Let me know if I can help you in some way > > Regards, > Andrea > > 2009/2/23 Carl Trieloff <[email protected]> > > > > > Sure, there is also a high level API in python for doing that. > > > > see: http://qpid.apache.org/qmf-python-console-tutorial.html > > > > Carl. > > > > > > GS.Chandra N wrote: > > > >> Carl, Thanks for the reply. > >> > >> Is there any way i can subscribe for these stats and aggregate them in a > >> normal python client, rather than learning qmf? I was under the > impression > >> that the broker was publishing these stats? > >> > >> Or can i talk QMF using python? > >> > >> Thanks > >> gs > >> > >> On Mon, Feb 23, 2009 at 8:10 PM, Carl Trieloff <[email protected] > >> >wrote: > >> > >> > >> > >>> GS.Chandra N wrote: > >>> > >>> > >>> > >>>> Hi, > >>>> > >>>> I 'm trying to setup a performance load testing framework for > evaluating > >>>> the > >>>> subscription performance and I need to measure the load rates. > >>>> > >>>> The reason i need this is that i'm trying to bombard my broker from > >>>> multiple > >>>> sources and i need to measure the single effective rate of incoming > >>>> messages > >>>> at the broker end. > >>>> > >>>> The qpid-queue-stats tools gives me the enque rate, but i cannot use > >>>> this > >>>> because i'm not trying to enqueu everything i recieve onto other > >>>> subscribers > >>>> due to infrastructure bottle-necks. (maybe later but not right now). > >>>> > >>>> Is there any way i can get this rate from the broker? What other stats > >>>> are > >>>> available from the broker? > >>>> > >>>> Thanks > >>>> gs > >>>> > >>>> > >>>> > >>>> > >>>> > >>> There are a tone of stats, I am note sure there is a broker wide load > >>> number however, that would need to be aggregated > >>> I would think. All the rate info for each connection or queue can be > >>> retrieved via QMF and then it can aggregated. > >>> > >>> Best would be to use qpid-tool to find the stat to aggregate and then > >>> write > >>> a QMF client to pull those stats, connection can > >>> give you in bytes. > >>> > >>> qpid: show connection > >>> > >>> Object of type org.apache.qpid.broker:connection: (last sample time: > >>> 14:20:32) > >>> Type Element 110 > >>> ============================================== > >>> property vhostRef 103 > >>> property address 127.0.0.1:60869 > >>> property incoming True > >>> property SystemConnection False > >>> property federationLink False > >>> property authIdentity gu...@qpid > >>> statistic closing False > >>> statistic framesFromClient 61 > >>> statistic framesToClient 0 > >>> statistic bytesFromClient 3648 > >>> statistic bytesToClient 0 > >>> qpid: > >>> > >>> > >>> An easier way would be to use the data off the exchanges, as their are > >>> less > >>> of them to aggregate. > >>> > >>> > >>> qpid: show exchange > >>> Object of type org.apache.qpid.broker:exchange: (last sample time: > >>> 14:22:42) > >>> Type Element 104 105 106 107 > >>> 108 109 > >>> > >>> > >>> > ===================================================================================================== > >>> property vhostRef 103 103 103 103 > >>> 103 103 > >>> property name qpid.management amq.direct > >>> amq.topic amq.fanout amq.match > >>> property type direct topic direct > topic > >>> fanout headers > >>> property durable False False True > True > >>> True True > >>> property arguments {} {} {} {} > >>> {} {} > >>> statistic producerCount 0 0 0 0 > >>> 0 0 > >>> statistic producerCountHigh 0 0 0 0 > >>> 0 0 > >>> statistic producerCountLow 0 0 0 0 > >>> 0 0 > >>> statistic bindingCount 2 2 1 0 > >>> 0 0 > >>> statistic bindingCountHigh 2 2 1 0 > >>> 0 0 > >>> statistic bindingCountLow 0 0 0 0 > >>> 0 0 > >>> statistic msgReceives 0 108 39 0 > >>> 0 0 > >>> statistic msgDrops 0 24 0 0 > >>> 0 0 > >>> statistic msgRoutes 0 84 39 0 > >>> 0 0 > >>> statistic byteReceives 0 15398 14254 0 > >>> 0 0 > >>> statistic byteDrops 0 3390 0 0 > >>> 0 0 > >>> statistic byteRoutes 0 12008 14254 0 > >>> 0 0 > >>> qpid: > >>> > >>> > >>> regards, > >>> Carl. > >>> > >>> > >>> --------------------------------------------------------------------- > >>> Apache Qpid - AMQP Messaging Implementation > >>> Project: http://qpid.apache.org > >>> Use/Interact: mailto:[email protected] > >>> > >>> > >>> > >>> > >> > >> > >> > > > > >
