-
Notifications
You must be signed in to change notification settings - Fork 541
fix: Do not call before_send for transactions #731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Got a test failure in https://travis-ci.com/github/getsentry/sentry-python/jobs/352702298#L1612-L1616 Quick glance at the test implementation and I guess it could be flakey. cc @untitaker |
This matches the behavior with JS and the specs in https://develop.sentry.dev/sdk/unified-api/tracing
46ad44b
to
82c5a05
Compare
Rebased to fix merge conflict. |
Is there a standard way to filter out transactions now? I've got all my backend endpoint handler entry points wrapped in spans and need to silence a few unimportant ones to save $$$ on the events quota. |
@vmarkovtsev you can use This is a workaround. Keep in mind that manually sampling transactions will potentially skew the aggregate metrics you see in Sentry. |
@vmarkovtsev also worth noting that event processors run right before the transaction is sent, which means that the sampling decision has already been propagated to other services for the life time of the transaction. It might or might not be of importance to you. If you're doing manual instrumentation, you should also be able to override the sampling decision early on by starting a transaction with We're working on a more general solution for controlling transaction sampling from SDKs. |
In my case, I am using Thanks for the workaround! It should work fine for me 👍 |
This matches the behavior with JS and the specs.
The change in JS was introduced in getsentry/sentry-javascript#2600.
See notes under "Few other fixes".