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

Claus Ibsen edited comment on CAMEL-12450 at 3/8/19 10:03 AM:
--------------------------------------------------------------

- Step EIP *DONE*
- Step MBean *DONE*
- XML DSL unit test *DONE*
- Dump step statistics *DONE*
- Dump step statistics JMX *DONE*
- Step events *DONE*
- StepId on MDC *DONE*
- StepId on processor mbean *DONE*
- StepId in exchange property / expression builder / simple language *DONE*
- Step EIP documentation *DONE*
- Karaf Step command *DONE* 


was (Author: davsclaus):
- Step EIP *DONE*
- Step MBean *DONE*
- XML DSL unit test *DONE*
- Dump step statistics *DONE*
- Dump step statistics JMX *DONE*
- Step events *DONE*
- StepId on MDC *DONE*
- StepId on processor mbean *DONE*
- StepId in exchange property / expression builder / simple language *DONE*
- Step EIP documentation *DONE*
- Karaf Step command (optional)
 

> Ability to group processors and gather related metrics 
> -------------------------------------------------------
>
>                 Key: CAMEL-12450
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12450
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, eip
>            Reporter: Luca Burgazzoli
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> It would be nice if we can add some marker inside a route to group logical 
> processors together and gather related metrics:
> As example:
> {code}
> from(...)
>     .step("step-id")
>         .process(...)
>         .to(...)
>     .end()
> {code}
> Then we need to have some custom events like:
> - StepStartedEvent
> - StepCompletedEvent
> - StepFailedEvent
> The people may be able to determine how long a logical step has last, if it 
> has a failure, the number of exchanges processed so far and so on



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to