Fix InstrumentedRecordInterceptor closing the trace too early #11471
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Spring Kafka InstrumentedRecordInterceptor was closing the trace before calling the decorated RecordInterceptor.
We print logs and do some other tasks inside the Kafka RecordInterceptor, especially if a failure occured after consuming an event.
This caused our logs not to be part of the trace when the kafka event got finished successfully or with failures.