Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.2.0
-
Fix Version/s: 1.3.0-BC
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Fix Version/s | 1.2.1 [ 10874 ] |
| Link | This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ] |
| Description | The flow tracing activation should be propagated from the service provider side to the service consumer side. The exchange property 'org.ow2.petals.monitoring.activate-flow-tracing' must be copied only if the flow tracing activation propagation is enabled in the incoming message exchange or on the service provider side. |
The Petals SE Camel must support the MONIT trace filtering.
Moreover, if defined in the incoming exchange, the flow tracing activation should be propagated from the service provider side to the service consumer side according to the flow tracing activation propagation defined in the service consumer definition or at component configuration. |
| Description |
The Petals SE Camel must support the MONIT trace filtering.
Moreover, if defined in the incoming exchange, the flow tracing activation should be propagated from the service provider side to the service consumer side according to the flow tracing activation propagation defined in the service consumer definition or at component configuration. |
The Petals SE Camel must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if defined in the incoming exchange, the flow tracing activation should be propagated from the service provider side to the service consumer side according to the flow tracing activation propagation defined in the service consumer definition or at component configuration. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Support of MONIT trace filtering added in master with unit tests. As the unit tests cover all combinations of flow tracing configuration a dedicated integration test is not needed.