Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.4.0-BC
-
Fix Version/s: 2.4.0-BC
-
Component/s: Consumer mode, Provider mode
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ] |
| Priority | Major [ 3 ] | |
| Description |
The Petals BC REST must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming HTTP REST Request exchange contains the HTTP header '{{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 Petals BC REST must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming HTTP REST request contains the HTTP header '{{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. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link |
This issue depends on |
| Description |
The Petals BC REST must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming HTTP REST request contains the HTTP header '{{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 Petals BC REST must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming HTTP REST request contains the HTTP header '{{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 at defined service consumer level or component configuration level. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.5.0-BC [ 10903 ] | |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Support of MONIT trace filtering on provider side added in trunk with unit tests. As the unit tests cover all combinations of flow tracing configuration, a dedicated integration test is not needed.