Hi Asanka, +1 for Using Dropwizard Metrics. I believe you can still continue to use Carbon Metrics [1], which is a wrapper for Dropwizard Metrics, including OSGi support, standard Carbon YAML configuration, Easy configuration support for multiple reporters, Support for dynamically enable/disable metrics.
[1] https://github.com/wso2/carbon-metrics On Mon, Jan 22, 2018 at 10:21 AM, Hasitha Hiranya <hasit...@wso2.com> wrote: > Hi Asanka, > > I think we also need to provide > > 1. publishing message rate by a publisher (publisher channel) > 2. subscribing message rate by a consumer (consumer channel) > 3. acknowledgement rate by a consumer (consumer channel) > > These stats are important when come to fine-tuning MB to deliver max > performance. > > Thanks > > On Mon, Jan 22, 2018 at 10:09 AM, Asanka Abeyweera <asank...@wso2.com> > wrote: > >> Hi all, >> >> We need to expose messaging metrics to provide information about the >> broker state. We are planning to expose following messaging metrics. >> >> - Queue >> - Number of messages >> - Number of messages in a specific queue* >> - Number of subscribers for a specific queue* >> - Total messages published (enqueued) >> - Number of messages published to a queue* >> - Total messages acknowledged (dequeued) >> - Number of messages acknowledged in a queue* >> - Exchanges >> - Total messages published >> - Number of messages published with a certain routing key* >> - Subscriptions >> - Total subscribers >> - Number of pending messages* >> - Total messages fetched* >> - Total messages acknowledged* >> - Total messages rejected* >> - Database >> - Read latency >> - Write latency >> - Delete latency >> - Read throughput >> - Write throughput >> - Delete throughput >> - Broker >> - Messages in inbound netty pipeline >> - Messages in data cache layer >> >> * - We will have to evaluate calculating dynamic metrics since it can >> depend on the library support and performance impact on the broker. >> >> Please suggest other messaging metrics we need to expose. >> >> The metric calculation should not have a considerable negative impact on >> the broker performance. We are planning to use the Metrics library [1] >> since it is known to have a low footprint on the performance. >> >> WDYT? >> [1]. http://isuru-perera.blogspot.com/2014/11/java-performance-mo >> nitoring-libraries.html >> [2]. https://github.com/dropwizard/metrics >> >> -- >> Asanka Abeyweera >> Associate Technical Lead >> WSO2 Inc. >> >> Phone: +94 712228648 <071%20222%208648> >> Blog: a5anka.github.io >> >> <https://wso2.com/signature> >> > > > > -- > *Hasitha Abeykoon* > Associate Technical Lead; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > -- Isuru Perera Technical Lead | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
