Currently, ConsumeExt flow traces are used both to denote an external event arriving in the bus and the send of an exchange into the bus.
It could make sense to differentiate the two: a trace to log the external event (ConsumeExtFlow) and a trace to log the moment an exchange is sent to bus (ConsumeFlow).
An example is if an error occurs before the exchange is sent (e.g., the SOAP BC receive a request which is mapped to nothing, so only ConsumeExt traces are logged).
ConsumeFlow is actually redundant with ProvideFlow, but there could be those reasons for it to exist:
- it enables to know in case of failure if a problem happened before the exchange was sent (before ConsumeFlow is logged) or after.
- it enables to compute the processing time of a component (before ConsumeFlow is logged) versus the time for transport (until ProvideFlow is logged).
Nevertheless, introducing the ConsumeFlow seems awkward for the following reasons:
- the aforementionned justifications are not business but technical
- this would mean there is two steps for the processing of a given service (the ConsumeExt then the Consume even though conceptually there is only one step happening)
Hence, we won't introduce ConsumeFlow for now but simply simplify the ConsumeExt and log it earlier.
Improvement Request
Resolved
Major
