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-monitoring-libraries.html
[2]. https://github.com/dropwizard/metrics
--
Asanka Abeyweera
Associate Technical Lead
WSO2 Inc.
Phone: +94 712228648
Blog: a5anka.github.io
<https://wso2.com/signature>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
