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

Claus Ibsen commented on CAMEL-12450:
-------------------------------------

We could let the steps be registered in JMX under "steps" folder instead of 
"processors", then its easier to query the JMX tree to find those for tooling 
that want to grab stats via JMX. And we can also add SB actuator endpoint that 
can dump the step stats specially.

[~lb] if you wanna take a stab at this, then you just extend PipelineDefinition 
and add it in the Java DSL in similar places where we have pipeline. We may 
want to enforce the step id so its in Java DSL always just .step("myId").

For JMX then if we add it under "steps" then you need to do a little bit of 
check and use that mbean name instead, but we can do that in a separate PR.

Naming in IT is hard, but I like the word step. I do think to keep it simpler 
we should do like pipeline, that the end of a step is using end, eg so you 
cannot interleave and mixup them

   begin step a

      begin step b

     end step a

  end step b

But you can stack them like

   begin step a

     begin step b

     end

  end

And we just name it step

   step a

     step b

     end

  end

 

Another name instead of step, can be group, block, action etc. 

> 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
>            Reporter: Luca Burgazzoli
>            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(...)
>     .beginStep("step-id")
>         .process(...)
>         .to(...)
>     .endStep("step-id")
> {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