Replies: 1 comment 1 reply
-
@ivantopo I made a small reproduction repo that shows it. It doesn't spin up a mysql instance, so you'll need one handy, but if you run the app and supply a database, user, pass and dest (localhost:3306) it will print the context keys which aren't carried from one pool to the next. https://github.com/dispalt/finagle-mysql-kamon/blob/master/src/main/scala/App.scala |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am not entirely sure how to fix this, so I thought I'd get some help.
I have a play service that calls Finagle MySQL instance, after that particular call most of the tracing information is lost. How do I know? I added log messages to see and I can see the trace information is lost.
Here's a simplified set of log messages:
test 1 is before the finagle call.
test 2 is right after
I generate a stack trace to show you the callstack at that point
test 3 is after converting it to an
IO
the last message is logged in play after the request is done (which has the retained context).
What I've tried to do to fix this:
executor-service-capture-on-submit
and disableexecutor-service
Would love some help on figuring this out!
Beta Was this translation helpful? Give feedback.
All reactions