Petals BC REST

Support of MONIT trace filtering

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4.0-BC
  • Fix Version/s: 2.4.0-BC
  • Security Level: Public
  • Description:
    Hide

    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.
    Show
    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.
  • Environment:
    -

Issue Links

Activity

Christophe DENEUX made changes - Wed, 18 Mar 2020 - 11:40:41 +0100
Field Original Value New Value
Link This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ]
Christophe DENEUX made changes - Wed, 18 Mar 2020 - 11:41:57 +0100
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.
Christophe DENEUX made changes - Wed, 18 Mar 2020 - 11:42:03 +0100
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Wed, 18 Mar 2020 - 11:42:04 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Fri, 27 Mar 2020 - 13:01:27 +0100
Link This issue depends on PETALSBCREST-84 [ PETALSBCREST-84 ]
Christophe DENEUX made changes - Mon, 30 Mar 2020 - 10:44:34 +0200
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.
Christophe DENEUX made changes - Tue, 31 Mar 2020 - 11:48:16 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.5.0-BC [ 10903 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Wed, 18 Mar 2020 - 11:40:00 +0100
    Updated:
    Tue, 31 Mar 2020 - 11:48:29 +0200
    Resolved:
    Tue, 31 Mar 2020 - 11:48:15 +0200