sentry-rust
sentry-rust copied to clipboard
Refactoring tracing span activation/deactivation
This is proposal how to improve tracing layer to handle concurrency better
This changes logic of transaction activation/deactivation from being tied to ctor/dtor and instead tied to enter/exit
The reason being is that if you have multiple transactions running concurrently, there is no way to distinguish for sentry this scenario as it just creates new child transaction every time parent is present
Partially Fixes #675