Petals SE EIP

Support of MONIT trace filtering

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.10.0
  • Fix Version/s: 2.11.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The Petals SE EIP 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.

    Show
    The Petals SE EIP 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.
  • Environment:
    -

Issue Links

Activity

Christophe DENEUX made changes - Thu, 10 Jan 2019 - 15:14:05 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Thu, 10 Jan 2019 - 15:14:07 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 10 Jan 2019 - 15:14:14 +0100
Fix Version/s 2.10.1 [ 10895 ]
Christophe DENEUX made changes - Thu, 10 Jan 2019 - 15:17:07 +0100
Link This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ]
Christophe DENEUX made changes - Thu, 10 Jan 2019 - 16:10:54 +0100
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. 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.
Hide
Christophe DENEUX added a comment - Thu, 10 Jan 2019 - 16:13:25 +0100 - edited

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Scatter-Gather'. As the unit tests cover all combinations of flow tracing configuration a dedicated integration test is not needed.

Show
Christophe DENEUX added a comment - Thu, 10 Jan 2019 - 16:13:25 +0100 - edited Support of MONIT trace filtering added in trunk with unit tests for pattern 'Scatter-Gather'. As the unit tests cover all combinations of flow tracing configuration a dedicated integration test is not needed.
Christophe DENEUX made changes - Thu, 10 Jan 2019 - 16:13:25 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Hide
Christophe DENEUX added a comment - Fri, 11 Jan 2019 - 09:10:34 +0100 - edited

Reopened to add support for others patterns, and to add user documentation.

Show
Christophe DENEUX added a comment - Fri, 11 Jan 2019 - 09:10:34 +0100 - edited Reopened to add support for others patterns, and to add user documentation.
Christophe DENEUX made changes - Fri, 11 Jan 2019 - 09:10:34 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 11 Jan 2019 - 10:06:06 +0100
Description 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 EIP 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.
Christophe DENEUX made changes - Wed, 30 Jan 2019 - 15:37:04 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Thu, 31 Jan 2019 - 11:05:47 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Dispatcher'

Show
Christophe DENEUX added a comment - Thu, 31 Jan 2019 - 11:05:47 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Dispatcher'
Hide
Christophe DENEUX added a comment - Thu, 31 Jan 2019 - 14:14:26 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Routing-Slip'

Show
Christophe DENEUX added a comment - Thu, 31 Jan 2019 - 14:14:26 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Routing-Slip'
Hide
Christophe DENEUX added a comment - Fri, 1 Feb 2019 - 14:24:39 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Wire-Tap'

Show
Christophe DENEUX added a comment - Fri, 1 Feb 2019 - 14:24:39 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Wire-Tap'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 08:57:23 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Router'

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 08:57:23 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Router'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 10:26:45 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Dynamic-Router'

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 10:26:45 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Dynamic-Router'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 10:26:55 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Bridge'

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 10:26:55 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Bridge'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 11:21:01 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Splitter'

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 11:21:01 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Splitter'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 12:42:10 +0100

Support of MONIT trace filtering added in trunk with unit tests for pattern 'Aggregator'

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 12:42:10 +0100 Support of MONIT trace filtering added in trunk with unit tests for pattern 'Aggregator'
Hide
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 14:52:09 +0100

All patterns now support flow tracing activation, and user documentation was updated.

Show
Christophe DENEUX added a comment - Mon, 4 Feb 2019 - 14:52:09 +0100 All patterns now support flow tracing activation, and user documentation was updated.
Christophe DENEUX made changes - Mon, 4 Feb 2019 - 14:52:09 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
7s
1
Christophe DENEUX
Thu, 10 Jan 2019 - 15:14:05 +0100
Open Open In Progress In Progress
2s
1
Christophe DENEUX
Thu, 10 Jan 2019 - 15:14:07 +0100
In Progress In Progress Resolved Resolved
59m 18s
1
Christophe DENEUX
Thu, 10 Jan 2019 - 16:13:25 +0100
Resolved Resolved Open Open
16h 57m
1
Christophe DENEUX
Fri, 11 Jan 2019 - 09:10:34 +0100
Open Open In Progress In Progress
19d 6h 26m
1
Christophe DENEUX
Wed, 30 Jan 2019 - 15:37:04 +0100
In Progress In Progress Resolved Resolved
4d 23h 15m
1
Christophe DENEUX
Mon, 4 Feb 2019 - 14:52:09 +0100



People

Dates

  • Created:
    Thu, 10 Jan 2019 - 15:13:58 +0100
    Updated:
    Mon, 4 Feb 2019 - 14:52:09 +0100
    Resolved:
    Mon, 4 Feb 2019 - 14:52:09 +0100