You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2011/08/25 07:38:30 UTC

[jira] [Created] (APLO-78) Provide message statistics (for topics) in the REST API

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
            Reporter: Lionel Cons


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

        

[jira] [Updated] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-78:
------------------------------

    Fix Version/s:     (was: 1.1)
                   1.0-beta5

> 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
>            Reporter: Lionel Cons
>             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

        

[jira] [Updated] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-78:
------------------------------

    Fix Version/s: 1.1

> 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
>            Reporter: Lionel Cons
>             Fix For: 1.1
>
>
> 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

        

[jira] [Updated] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-78:
------------------------------

    Component/s: apollo-web
                 apollo-dto
                 apollo-broker

> 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

        

[jira] [Updated] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-78:
------------------------------

    Affects Version/s: 1.0-beta5
        Fix Version/s:     (was: 1.0-beta5)
                       1.0

beta 5 is going to have metrics on topics, but they are a little broken in some scenarios like when you are spooling to queues.  Fixed now.

> 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
>    Affects Versions: 1.0-beta5
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0
>
>
> 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

        

[jira] [Resolved] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-78.
-------------------------------

    Resolution: Fixed
      Assignee: Hiram Chirino

> 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

        

[jira] [Resolved] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-78.
-------------------------------

    Resolution: Fixed
    
> 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
>    Affects Versions: 1.0-beta5
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta6
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-78:
------------------------------

    Fix Version/s:     (was: 1.0)
                   1.0-beta6
    
> 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
>    Affects Versions: 1.0-beta5
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta6
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (APLO-78) Provide message statistics (for topics) in the REST API

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ 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