Reactive logging request/response having request/response logs with span and trace ids zeroes #9556
Replies: 3 comments 10 replies
-
Please provide a minimal sample application that reproduces the issue. |
Beta Was this translation helpful? Give feedback.
1 reply
-
maybe related to #7739 |
Beta Was this translation helpful? Give feedback.
1 reply
-
@trask Not sure if there is a correlation in between. @laurit Attaching the demo project describing the issue. Sorry for bad code, everything is within root package. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are having reactive context, so followed lates PR ( opentelemetry-java-instrumentation) to accommodate the solution as we are still using spring-boot 3.0.6.
Implemented:
also to mentioned that having
Ordered.HIGHEST_PRECEDENCE + 1
will actually get blocked in:!instrumenter.shouldStart(parentContext, exchange)
After this filter, in the chain is decorator filter, having main purpose of logging request/response:
subscribe to new context:
After subscribe calling
Context.current()
directly after in the next in chain filter will return empty context, but nothing in the decorators request logs nothing, response logs, only"traceId":"00000000000000000000000000000000","spanId":"0000000000000000"
Configuration looks like:
Having request/response logged as:
Thanks for replies in advance.
Beta Was this translation helpful? Give feedback.
All reactions