You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2011/08/30 01:48:37 UTC
[jira] [Reopened] (APLO-78) Provide message statistics (for topics)
in the REST API
[ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino reopened APLO-78:
-------------------------------
Topic metrics don't make sense when used with slow producer policy = queue.
> Provide message statistics (for topics) in the REST API
> -------------------------------------------------------
>
> Key: APLO-78
> URL: https://issues.apache.org/jira/browse/APLO-78
> Project: ActiveMQ Apollo
> Issue Type: Improvement
> Components: apollo-broker, apollo-dto, apollo-web
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.0-beta5
>
>
> The aggregated queue metrics (/broker/queue-metrics) are very useful to understand how the broker works as a whole.
> However, they seem to contain only queue information (and probably dsub information, please confirm) but not topic information.
> For monitoring purposes, it would be useful to also collect the received/sent messages (with count/size) on all topics.
> This way, one could for instance find out how many messages are received by the broker, per unit of time, to graph this information.
> This information should appear both per-topic (/broker/virtual-hosts/<name>/topics/<id>) and aggregated (/broker/topic-metrics?).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira