You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2012/09/22 00:46:07 UTC
[jira] [Created] (CAMEL-5637) Tracking/Waypoint Slip intercept
strategy
Raul Kripalani created CAMEL-5637:
-------------------------------------
Summary: Tracking/Waypoint Slip intercept strategy
Key: CAMEL-5637
URL: https://issues.apache.org/jira/browse/CAMEL-5637
Project: Camel
Issue Type: New Feature
Components: camel-core
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Priority: Minor
Fix For: 2.11.0
In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been.
Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5637) Tracking/Waypoint Slip intercept
strategy
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani updated CAMEL-5637:
----------------------------------
Description:
In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the routes and contexts where the Exchange has been.
Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
was:
In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been.
Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
> Tracking/Waypoint Slip intercept strategy
> -----------------------------------------
>
> Key: CAMEL-5637
> URL: https://issues.apache.org/jira/browse/CAMEL-5637
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Priority: Minor
> Fix For: 2.11.0
>
>
> In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
> A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the routes and contexts where the Exchange has been.
> Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
> It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-5637) Tracking/Waypoint Slip
intercept strategy
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461036#comment-13461036 ]
Claus Ibsen edited comment on CAMEL-5637 at 9/22/12 5:31 PM:
-------------------------------------------------------------
Raul, there is already support and logic for this.
eg hence why the Camel tracer can do what it does.
Its the message history EIP pattern
http://www.eaipatterns.com/MessageHistory.html
Its currently tied to UoW where you can get the trace nodes. For Camel 3.0 we have on the roadmap to refactor this logic, and introduce a better end user API for that as well.
http://camel.apache.org/camel-30-roadmap.html
So IMHO dont introduce a new layer of code when there is already existing. By that I mean as underlying logic.
If you can add a intercepter that uses the existing UoW logic (eg would the tracer) then that is okay. But IMHO consider looking at what is there already first. We have to avoid "bloating" the core with to many features and functionality. And camel-core cannot support *every* end users use-case out of the box.
was (Author: davsclaus):
Raul, there is already support and logic for this.
eg hence why the Camel tracer can do what it does.
Its the message history EIP pattern
http://www.eaipatterns.com/MessageHistory.html
Its currently tied to UoW where you can get the trace nodes. For Camel 3.0 we have on the roadmap to refactor this logic, and introduce a better end user API for that as well.
http://camel.apache.org/camel-30-roadmap.html
So IMHO dont introduce a new layer of code when there is already existing.
> Tracking/Waypoint Slip intercept strategy
> -----------------------------------------
>
> Key: CAMEL-5637
> URL: https://issues.apache.org/jira/browse/CAMEL-5637
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Priority: Minor
> Fix For: 2.11.0
>
>
> In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
> A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been.
> Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
> It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5637) Tracking/Waypoint Slip intercept
strategy
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461036#comment-13461036 ]
Claus Ibsen commented on CAMEL-5637:
------------------------------------
Raul, there is already support and logic for this.
eg hence why the Camel tracer can do what it does.
Its the message history EIP pattern
http://www.eaipatterns.com/MessageHistory.html
Its currently tied to UoW where you can get the trace nodes. For Camel 3.0 we have on the roadmap to refactor this logic, and introduce a better end user API for that as well.
http://camel.apache.org/camel-30-roadmap.html
So IMHO dont introduce a new layer of code when there is already existing.
> Tracking/Waypoint Slip intercept strategy
> -----------------------------------------
>
> Key: CAMEL-5637
> URL: https://issues.apache.org/jira/browse/CAMEL-5637
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Priority: Minor
> Fix For: 2.11.0
>
>
> In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
> A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been.
> Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
> It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5637) Tracking/Waypoint Slip intercept
strategy
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468191#comment-13468191 ]
Raul Kripalani commented on CAMEL-5637:
---------------------------------------
Hey Claus,
The intention of this ticket is different: the grain of tracing is not processor nodes, but routes and contexts. In a layered architecture, a message typically passes through a number of routes until it reaches its final destination.
I'd like to build a feature for Camel to keep track of all the routes and contexts that have 'seen' that message. This entails propagating a new header like the breadcrumbId, so that all UoWs can add their routes to it. The data structure needs to be serialisable.
It's an analogy to AMQ's brokerPath or TIBCO's tracking Id token.
Regards,
Raúl.
> Tracking/Waypoint Slip intercept strategy
> -----------------------------------------
>
> Key: CAMEL-5637
> URL: https://issues.apache.org/jira/browse/CAMEL-5637
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Priority: Minor
> Fix For: 2.11.0
>
>
> In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing.
> A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been.
> Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}.
> It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira