On Sun, 17 Nov 2019 at 22:37, VERMEULEN Olivier <[email protected]> wrote:
> Thanks Rob. > > This will help us a lot in monitoring the brokers. > By the way, any chance we can get something similar on the dispatch-router > side? > Probably worth starting a separate thread on that topic, as it's likely that the Dispatch developers will skip this thread due to its title :-) -- Rob > > Olivier > > -----Original Message----- > From: Rob Godfrey <[email protected]> > Sent: dimanche 17 novembre 2019 13:36 > To: [email protected] > Subject: Re: Broker-J statistics and CPU consumption > > I've created the JIRA QPID-8376 > <https://issues.apache.org/jira/browse/QPID-8376> and made a change there > which adds two statistics - processCpuTime (which is the cumulative CPU > time since the app started) and processCpuLoad (which is the current CPU > load due to the process, rounded to 4 decimal places) which will be > retrieved if the underlying Java platform supports them. > > Hope this helps, > Rob > > On Fri, 15 Nov 2019 at 23:05, Rob Godfrey <[email protected]> wrote: > > > > > > > On Fri, 15 Nov 2019 at 21:21, Oleksandr Rudyy <[email protected]> wrote: > > > >> Hi Olivier, > >> > >> CPU consumption statistic is not available. > >> Potentially, cpu average load from > >> java.lang.management.OperatingSystemMXBean#getSystemLoadAverage can > >> be returned as part of broker statistics. > >> If you need OperatingSystemMXBean#getSystemLoadAverage() being > >> exposed as broker statistic, please raise JIRA. > >> > > > > I'm not sure there is huge value in reporting on the SystemLoadAverage > > - that is the total load on the system, rather than just the load the > > Broker is generating I think. As such it seems weird to ask the > > Broker to report on it. As per my (very slightly earlier than yours) > > mail - there does seem to be a mechanism on at least some Sun/Oracle > > JVMs to get the Process CPU time. Again I'm still somewhat dubious as > > to whether this should be gather from the broker itself, or whether > > this is more properly reported using some sort of external monitoring > tool. > > > > -- Rob > > > > > >> > >> Kind Regards, > >> Alex > >> > >> On Fri, 15 Nov 2019 at 16:31, VERMEULEN Olivier < > >> [email protected]> > >> wrote: > >> > >> > Hello, > >> > > >> > We're using the Broker-J 7.1.3. > >> > Looking at the statistics provided by > >> > /api/latest/broker/getStatistics, > >> I > >> > don't see anything related to the CPU consumption. > >> > Did I miss something or this information is not provided? > >> > > >> > Thanks, > >> > Olivier > >> > ******************************* > >> > This e-mail contains information for the intended recipient only. > >> > It may contain proprietary material or confidential information. If > >> > you are not the intended recipient you are not authorized to > >> > distribute, copy or use this e-mail or any attachment to it. Murex > >> > cannot guarantee that it is virus free and accepts no > >> > responsibility for any loss or damage arising from its use. If you > >> > have received this e-mail in error please notify immediately the > >> > sender and delete the original email received, any attachments and > all copies from your system. > >> > > >> > > > ******************************* > This e-mail contains information for the intended recipient only. It may > contain proprietary material or confidential information. If you are not > the intended recipient you are not authorized to distribute, copy or use > this e-mail or any attachment to it. Murex cannot guarantee that it is > virus free and accepts no responsibility for any loss or damage arising > from its use. If you have received this e-mail in error please notify > immediately the sender and delete the original email received, any > attachments and all copies from your system. >
