Petals BC Gateway

Support of MONIT trace filtering

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.0
  • Fix Version/s: 1.2.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    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.

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

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 25 Mar 2022 - 13:36:13 +0100

User documentation updated

Show
Christophe DENEUX added a comment - Fri, 25 Mar 2022 - 13:36:13 +0100 User documentation updated
Hide
Permalink
Christophe DENEUX added a comment - Wed, 10 Jun 2020 - 11:51:03 +0200

Reopened to update use documentation

Show
Christophe DENEUX added a comment - Wed, 10 Jun 2020 - 11:51:03 +0200 Reopened to update use documentation
Hide
Permalink
Christophe DENEUX added a comment - Wed, 10 Jun 2020 - 11:48:57 +0200 - edited

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.

Show
Christophe DENEUX added a comment - Wed, 10 Jun 2020 - 11:48:57 +0200 - edited 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.

People

Dates

  • Created:
    Tue, 8 Jan 2019 - 10:32:32 +0100
    Updated:
    Fri, 5 Apr 2024 - 15:22:48 +0200
    Resolved:
    Fri, 25 Mar 2022 - 13:36:13 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.