I merged the PRs (after the code review) On Thu, Jun 11, 2015 at 8:08 PM, Isuru Perera <[email protected]> wrote:
> Hi, > > I did necessary changes in carbon metrics [1] to support visualizing any > metric data. > > I created an OSGi Fragment bundle for Messaging Metrics UI. The Messaging > Metric UI now visualizes the metrics sent by Anuja in last email. > > I really appreciate if MB team can merge following PRs and test the > Metrics UI. > > https://github.com/wso2/carbon-business-messaging/pull/65 > https://github.com/wso2/product-mb/pull/120 > > Thanks! > > Best Regards, > > [1] https://github.com/wso2/carbon-metrics > > On Wed, Jun 3, 2015 at 4:17 PM, Anuja Herath <[email protected]> wrote: > >> Hi, >> >> Following metrics and categories will be used to draw graphs in MB. Each >> category will have one graph. >> >> *Disruptor* >> Total Messages in Inbound Disruptor - >> *org.wso2.mb.inbound.disruptor.message.count* >> Total Acks in Inbound Disruptor - >> *org.wso2.mb.inbound.disruptor.ack.count* >> Total Messages in Outbound Disruptor - >> *org.wso2.mb.outbound.disruptor.message.count* >> >> *Publish & Subscribe* >> Total Queue Subscribers - org.wso2.mb.queue.subscribers.count >> Total Topic Subscribers - *org.wso2.mb.topic.subscribers.count* >> Total Channels - *org.wso2.mb.channels.active.count* >> >> *Message & Acknowledgements* >> Messages Received/sec - *org.wso2.mb.message.receive* >> Messages Published/sec - *org.wso2.mb.message.sent* >> Acknowledges Received /sec -* org.wso2.mb.ack.receive* >> Acknowledges Sent /sec - *org.wso2.mb.ack.sent* >> >> *Database* >> Database write latency - *org.wso2.mb.database.write* >> Database read latency - *org.wso2.mb.database.read* >> >> Thanks, >> Anuja. >> >> >> On Mon, Jun 1, 2015 at 4:55 PM, Isuru Perera <[email protected]> wrote: >> >>> Hi Ramith, >>> >>> I'm sorry I couldn't reply sooner. Currently there is no way to change >>> the individual metric levels at runtime. We will consider this in a future >>> release. >>> >>> There are ways to enable/disable whole metrics feature and set the root >>> level at runtime via JMX operations. >>> >>> Regarding metrics data, the JDBC reporter has a scheduled task to clean >>> up data in database after a configured period. For example, in the default >>> configuration, the clean up task is enabled and it is configured to keep >>> data only for 7 days. >>> >>> Do you have any more concerns? >>> >>> Thanks! >>> >>> Best Regards, >>> >>> On Fri, May 22, 2015 at 10:47 AM, Ramith Jayasinghe <[email protected]> >>> wrote: >>> >>>> I think knowing the state if inbound/outbound disruptors is important >>>> at the first look ( when trouble shooting). >>>> Shall we make that 'INFO' level. >>>> >>>> @IsuruP: Can we change matrics configs on the fly with out restarting >>>> the servers ( e.g. enable debug level stats) >>>> and will there be lots of logs/data accumulated over >>>> time with use of matrices library? >>>> regards >>>> Ramith >>>> >>>> On Fri, May 22, 2015 at 10:40 AM, Anuja Herath <[email protected]> wrote: >>>> >>>>> Hi All, >>>>> >>>>> We are going to add carbon metrics support for MB 3.0. After >>>>> implementing, we will be able to identify and troubleshoot bottlenecks at >>>>> different levels in MB easily. Following is the list of metrics that we >>>>> are >>>>> going to implement at initial stage. >>>>> >>>>> MetricLog LevelDescriptionMessages Received/secINFONumber of messages >>>>> recieved per second. This metric is calculated when a message reaches >>>>> server.Acknowledges Sent/secINFONumber of acknowledgments sent to >>>>> publishers per second.Total ChannelsINFOTotal number of active >>>>> channels.Messages Published/secINFONumber of message published per >>>>> second. This metrics is calculated when server publishes a message to a >>>>> subscriber.Acknowledges Received /secINFONumber of acknowledgments >>>>> received from publishers per second.Total ConsumersINFOTotal number >>>>> of active consumers.Database read latencyINFOAverage value of time >>>>> taken for database read calls.Database write latencyINFOAverage value >>>>> of time taken for database write calls.Total Messages in Inbound >>>>> DisruptorDEBUGCurrent number of messages in inbound disruptor.Total >>>>> Messages in Outbound DisruptorDEBUGCurrent number of messages in >>>>> outbound disruptor.Database latencies (Method Level)DEBUGOperation >>>>> wise latencies of database calls.Cluster Coordinator LatencyDEBUGLatency >>>>> of cluster coordination >>>>> >>>>> -- >>>>> Anuja Herath >>>>> *Software Engineer* >>>>> *WSO2, Inc.* >>>>> Mobile : +94 (0)71 429 8861 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ramith Jayasinghe >>>> Technical Lead >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> E: [email protected] >>>> P: +94 777542851 >>>> >>>> >>> >>> >>> -- >>> Isuru Perera >>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >>> Lean . Enterprise . Middleware >>> >>> about.me/chrishantha >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Anuja Herath >> *Software Engineer* >> *WSO2, Inc.* >> Mobile : +94 (0)71 429 8861 >> > > > > -- > Isuru Perera > Associate Technical Lead | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about> > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: [email protected] P: +94 777542851
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
