Alexander Dinauer
Alexander Dinauer
Hi @omurkartal, the switch to another thread should not be problematic if `SentryContext` is used. Same for multiple requests landing on the same thread. I'm able to reproduce the behaviour...
Adding more spans to `fun2` shows that it sometimes loses spans happening after the flow, so this might be related to flow after all. Haven't seen drops on a different...
Using `flowOn(SentryContext())` doesn't seem to change this behaviour.
Commenting out the flow in `fun2` seems to get rid of the problem, moving the flow and adding a span after it, causes problems again where the span after the...
An alternative here could be using our [OpenTelemetry integration](https://docs.sentry.io/platforms/java/guides/spring-boot/performance/instrumentation/opentelemetry/) and see if that works better.
Thanks for the update @omurkartal
Thanks for opening this issue @Akil17 we currently don't know of any replacement library for p6spy. We also have https://github.com/getsentry/sentry-java/issues/3179
We just discussed and what you could try is opening a PR in p6spy repo to forward `.toString()` in `PreparedStatementWrapper` to the delegate `PreparedStatement`. Not sure if they still merge...
> I would suggest Sentry can maintain its own p6spy branch if possible and by default add that as a dependency in the BE SDKs. If more problems with p6spy...
Is there a reason, you're calling `Sentry.init` manually? You should be able to set the logger, e.g. by exposing a `Sentry.OptionsConfiguration` bean that'll let you customize options programatically without having...