Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1.0
-
Fix Version/s: 1.2.0
-
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.1.1 [ 10891 ] |
| Link | This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ] |
| Summary | Flow tracing propagation through domains | Support of MONIT trace filtering |
| Description |
The flow tracing activation should be propagated from one consumer domain to provider domains.
Note: The exchange property {{}} must be copied only if the flow tracing activation propagation is enabled at service consumer level of the provider domain. |
If an incoming exchange contains the property '{{org.ow2.petals.monitoring.activate-flow-tracing}}', its value is used to enable/disabled flow tracing at service consumer level.
The flow tracing activation should be propagated from one consumer domain to provider domains. The exchange property '{{org.ow2.petals.monitoring.activate-flow-tracing}}' must be copied only if the flow tracing activation propagation is enabled at service consumer level of the provider domain. |
| Description |
If an incoming exchange contains the property '{{org.ow2.petals.monitoring.activate-flow-tracing}}', its value is used to enable/disabled flow tracing at service consumer level.
The flow tracing activation should be propagated from one consumer domain to provider domains. The exchange property '{{org.ow2.petals.monitoring.activate-flow-tracing}}' must be copied only if the flow tracing activation propagation is enabled at service consumer level of the provider domain. |
If an incoming exchange contains the property 'org.ow2.petals.monitoring.activate-flow-tracing':
* its value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined service consumer level or component configuration level. The flow tracing activation should be propagated from a consumer domain to the provider domain through the exchange property '{{org.ow2.petals.monitoring.activate-flow-tracing}}' of the outgoing exchange. The property is set according to the flow tracing activation propagation defined at service provider level or component configuration level. |
| Description |
If an incoming exchange contains the property 'org.ow2.petals.monitoring.activate-flow-tracing':
* its value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined service consumer level or component configuration level. The flow tracing activation should be propagated from a consumer domain to the provider domain through the exchange property '{{org.ow2.petals.monitoring.activate-flow-tracing}}' of the outgoing exchange. The property is set according to the flow tracing activation propagation defined at service provider level or component configuration level. |
The Petals BC Gateway must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming exchange contains the property 'org.ow2.petals.monitoring.activate-flow-tracing': * its value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined service consumer level or component configuration level. The flow tracing activation should be propagated from a consumer domain to the provider domain through the exchange property '{{org.ow2.petals.monitoring.activate-flow-tracing}}' of the outgoing exchange. The property is set according to the flow tracing activation propagation defined at service provider level or component configuration level. |
| 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 ] |
| Link |
This issue blocks |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Support of MONIT trace filtering on provider side added in master branch with unit tests. As the unit tests cover all combinations of flow tracing configuration, a dedicated integration test is not needed.