Petals SE Mapping

Support of MONIT trace filtering

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.0
  • Fix Version/s: 1.2.0
  • Component/s: Monitoring (Business)
  • Security Level: Public
  • Description:
    Hide

    The Petals SE Mapping 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 Mapping 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 - Mon, 14 Jan 2019 - 12:37:44 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Component/s Monitoring (Business) [ 10465 ]
Christophe DENEUX made changes - Mon, 14 Jan 2019 - 12:37:45 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Mon, 14 Jan 2019 - 12:38:00 +0100
Link This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ]
Hide
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 15:16:32 +0100 - edited

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.

Show
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 15:16:32 +0100 - edited 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.
Christophe DENEUX made changes - Wed, 16 Jan 2019 - 15:16:32 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.1.1 [ 10871 ]
Resolution Fixed [ 1 ]
Hide
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 15:18:10 +0100

Reopened to add user documentation.

Show
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 15:18:10 +0100 Reopened to add user documentation.
Christophe DENEUX made changes - Wed, 16 Jan 2019 - 15:18:10 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Wed, 16 Jan 2019 - 17:20:18 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 17:20:29 +0100

User documentation updated

Show
Christophe DENEUX added a comment - Wed, 16 Jan 2019 - 17:20:29 +0100 User documentation updated
Christophe DENEUX made changes - Wed, 16 Jan 2019 - 17:20:29 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 10 Mar 2023 - 10:57:40 +0100
Description The Petals SE Flowable must support the MONIT trace filtering (see PETALSDISTRIB-395).

Moreover, if defined in the incoming exchange creating new process instance, the flow tracing activation should be propagated to all service providers invoked during the process instance execution according to the flow tracing activation propagation defined in the service consumer definition or at component configuration.
The Petals SE Mapping 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.
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
42s
1
Christophe DENEUX
Mon, 14 Jan 2019 - 12:37:44 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Mon, 14 Jan 2019 - 12:37:45 +0100
In Progress In Progress Resolved Resolved
2d 2h 38m
1
Christophe DENEUX
Wed, 16 Jan 2019 - 15:16:32 +0100
Resolved Resolved Open Open
1m 38s
1
Christophe DENEUX
Wed, 16 Jan 2019 - 15:18:10 +0100
Open Open In Progress In Progress
2h 2m
1
Christophe DENEUX
Wed, 16 Jan 2019 - 17:20:18 +0100
In Progress In Progress Resolved Resolved
11s
1
Christophe DENEUX
Wed, 16 Jan 2019 - 17:20:29 +0100



People

Dates

  • Created:
    Mon, 14 Jan 2019 - 12:37:02 +0100
    Updated:
    Fri, 10 Mar 2023 - 10:57:40 +0100
    Resolved:
    Wed, 16 Jan 2019 - 17:20:29 +0100