Each service provider implemented is able to log MONIT traces:
* on service provider invocation, when receiving an incoming request, with following attributes:
** {{traceCode}} set to {{provideFlowStepBegin}},
** {{flowInstanceId}} set to the flow instance identifier retrieved from the incoming request,
** {{flowStepId}} set to an UUID value,
** {{flowStepInterfaceName}} set to the service provider interface name,
** {{flowStepServiceName}} set to the service provider service name,
** {{flowStepOperationName}} set to the operation of the invoked service provider,
** {{flowStepEndpointName}} set to the service provider endpoint name,
** {{flowPreviousStepId}} set to the step identifier of the previous step, retrieved from the incoming request.
* on service provider termination, when returning the outgoing response, with following attributes:
** {{traceCode}} set to {{provideFlowStepEnd}} or {{provideFlowStepFailure}},
** {{flowInstanceId}} set to the flow instance identifier retrieved from the incoming request,
** {{flowStepId}} set to the flow step identifier defined on incoming request receipt.

The flow tracing (ie. MONIT traces generation) is defined according to the property '{{org.ow2.petals.monitoring.business.activate-flow-tracing}}' of the incoming request. If the property does not exist, the parameter {{activate-flow-tracing}} of the service provider definition will be inspected. If no parameter is defined at service provider level, the component configuration parameter '{{activate-flow-tracing}}' is used. Finally, by default, the flow tracing is enabled.

The flow tracing propagation from a service provider implemented with this component to another service provider is driven by the parameter {{propagate-flow-tracing-activation}} of the service consumer definition. If no parameter is defined at service consumer level, the component configuration parameter '{{propagate-flow-tracing-activation}}' is used. Finally, by default, the flow tracing propagation is enabled.