You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Created) (JIRA)" <ji...@apache.org> on 2012/01/26 15:34:40 UTC
[jira] [Created] (CAMEL-4946) Management - Get performance
statistics as XML per CamelContext or per Route
Management - Get performance statistics as XML per CamelContext or per Route
----------------------------------------------------------------------------
Key: CAMEL-4946
URL: https://issues.apache.org/jira/browse/CAMEL-4946
Project: Camel
Issue Type: Improvement
Components: camel-core, jmx
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.10.0
Currently its harder for tooling such as JConsole, Camel Karaf Shell or others to gather performance statistics of a CamelContext and its routes, as you will have to use the JMX API and loop each route, and gather processors, and associate the processors with the route etc. And then use the fine grained attributes on the ManagedProcessorMBean to get the performance statistics.
This is a bit cumbersome, and also very chatty API calls, especially if the JMX is remoting, and it makes it slower to gather stats.
As we got XML outputs for bulk of data such as routes etc, we should have a single API call to get the full stats for the entire CamelContext, or per route basis. Using XML as return type, makes it much easier for any kind of tooling and language to use the data. Instead of tying to use the JMX OpenMBean structure which is Java only based.
SIDENOTE START:
For Camel 3.0 we should offer a JSON output with a REST based management API as well. But that would require a possible new camel-core-management component which as a JSON library in use such as Jackson.
SIDENOTE END:
--
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] [Commented] (CAMEL-4946) Management - Get performance
statistics as XML per CamelContext or per Route
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194070#comment-13194070 ]
Claus Ibsen commented on CAMEL-4946:
------------------------------------
Thanks for sharing this Preben. Jolokia looks really great.
> Management - Get performance statistics as XML per CamelContext or per Route
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4946
> URL: https://issues.apache.org/jira/browse/CAMEL-4946
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.10.0
>
>
> Currently its harder for tooling such as JConsole, Camel Karaf Shell or others to gather performance statistics of a CamelContext and its routes, as you will have to use the JMX API and loop each route, and gather processors, and associate the processors with the route etc. And then use the fine grained attributes on the ManagedProcessorMBean to get the performance statistics.
> This is a bit cumbersome, and also very chatty API calls, especially if the JMX is remoting, and it makes it slower to gather stats.
> As we got XML outputs for bulk of data such as routes etc, we should have a single API call to get the full stats for the entire CamelContext, or per route basis. Using XML as return type, makes it much easier for any kind of tooling and language to use the data. Instead of tying to use the JMX OpenMBean structure which is Java only based.
> SIDENOTE START:
> For Camel 3.0 we should offer a JSON output with a REST based management API as well. But that would require a possible new camel-core-management component which as a JSON library in use such as Jackson.
> SIDENOTE END:
--
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] [Commented] (CAMEL-4946) Management - Get performance
statistics as XML per CamelContext or per Route
Posted by "Preben Asmussen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194025#comment-13194025 ]
Preben Asmussen commented on CAMEL-4946:
----------------------------------------
Regarding the Sidenode have a look at Jolokia http://www.jolokia.org/
It offers remote Json jmx stats via a nice query interface.
One would not only be able to query Camel, but every managed bean in the jvm eg. ActiveMQ.
> Management - Get performance statistics as XML per CamelContext or per Route
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4946
> URL: https://issues.apache.org/jira/browse/CAMEL-4946
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.10.0
>
>
> Currently its harder for tooling such as JConsole, Camel Karaf Shell or others to gather performance statistics of a CamelContext and its routes, as you will have to use the JMX API and loop each route, and gather processors, and associate the processors with the route etc. And then use the fine grained attributes on the ManagedProcessorMBean to get the performance statistics.
> This is a bit cumbersome, and also very chatty API calls, especially if the JMX is remoting, and it makes it slower to gather stats.
> As we got XML outputs for bulk of data such as routes etc, we should have a single API call to get the full stats for the entire CamelContext, or per route basis. Using XML as return type, makes it much easier for any kind of tooling and language to use the data. Instead of tying to use the JMX OpenMBean structure which is Java only based.
> SIDENOTE START:
> For Camel 3.0 we should offer a JSON output with a REST based management API as well. But that would require a possible new camel-core-management component which as a JSON library in use such as Jackson.
> SIDENOTE END:
--
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] [Resolved] (CAMEL-4946) Management - Get performance
statistics as XML per CamelContext or per Route
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4946.
--------------------------------
Resolution: Fixed
> Management - Get performance statistics as XML per CamelContext or per Route
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4946
> URL: https://issues.apache.org/jira/browse/CAMEL-4946
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.10.0
>
>
> Currently its harder for tooling such as JConsole, Camel Karaf Shell or others to gather performance statistics of a CamelContext and its routes, as you will have to use the JMX API and loop each route, and gather processors, and associate the processors with the route etc. And then use the fine grained attributes on the ManagedProcessorMBean to get the performance statistics.
> This is a bit cumbersome, and also very chatty API calls, especially if the JMX is remoting, and it makes it slower to gather stats.
> As we got XML outputs for bulk of data such as routes etc, we should have a single API call to get the full stats for the entire CamelContext, or per route basis. Using XML as return type, makes it much easier for any kind of tooling and language to use the data. Instead of tying to use the JMX OpenMBean structure which is Java only based.
> SIDENOTE START:
> For Camel 3.0 we should offer a JSON output with a REST based management API as well. But that would require a possible new camel-core-management component which as a JSON library in use such as Jackson.
> SIDENOTE END:
--
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