We are having an issue where some of our transactions are being sent to Sentry even though we have "disabled" sampling by setting config.traces_sample_rate to 0.0.
It doesn’t seem to happen consistently and is difficult to reproduce. We are not making any calls to capture_* directly.
Is there any way to disable transactions altogether? Or have you any idea why these might be getting sent?
In terms of logs we are getting a lot of INFO -- sentry: Sending transaction xxxxxxxxx to Sentry but we aren’t getting any of the logs pertaining to sampling around https://github.com/getsentry/sentry-ruby/blob/master/sentry-ruby/lib/sentry/transaction.rb#L71-L117 so I am assuming the config is set up correctly and sampling is as good as "disabled" but somehow transactions are getting sent by some other means.
Running on:
sentry-ruby-core (4.2.2)
sentry-rails (4.2.2)
sentry-ruby (4.2.2)
We are having an issue where some of our transactions are being sent to Sentry even though we have "disabled" sampling by setting
config.traces_sample_rateto0.0.It doesn’t seem to happen consistently and is difficult to reproduce. We are not making any calls to
capture_*directly.Is there any way to disable transactions altogether? Or have you any idea why these might be getting sent?
In terms of logs we are getting a lot of
INFO -- sentry: Sending transaction xxxxxxxxx to Sentrybut we aren’t getting any of the logs pertaining to sampling around https://github.com/getsentry/sentry-ruby/blob/master/sentry-ruby/lib/sentry/transaction.rb#L71-L117 so I am assuming the config is set up correctly and sampling is as good as "disabled" but somehow transactions are getting sent by some other means.Running on:
sentry-ruby-core (4.2.2)
sentry-rails (4.2.2)
sentry-ruby (4.2.2)