You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2017/08/07 15:04:00 UTC

[jira] [Commented] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController

    [ https://issues.apache.org/jira/browse/CAMEL-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116704#comment-16116704 ] 

Luca Burgazzoli commented on CAMEL-11580:
-----------------------------------------

I'm going to split this in two parts:

- this jira to provide a minimal JMX/Endpoint support for plain RouteController 
- a new JIRA to support SupervisingRouteController


> Add JMX api RouteController and SupervisingRouteController
> ----------------------------------------------------------
>
>                 Key: CAMEL-11580
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11580
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, jmx
>            Reporter: Claus Ibsen
>            Assignee: Luca Burgazzoli
>              Labels: route-controller
>             Fix For: 2.20.0
>
>
> We should have some JMX API that can expose the state of the route, with JMX attributes. Then there should be an extended for SupervisingRouteController which can shows the state of each of those routes, and the backoff configuration etc.
> eg today there is little visibility for end users what is going on with the SupervisingRouteController. We need to expose that in JMX.
> Then we can leverage that also for Spring Boot and have an actuator endpoint (/camel/route-controller) where we can report this state as json.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)