To set up or configure our Dynamic Sampling feature, you need to be an Owner, Manager, or Admin of your Sentry organization.
The Dynamic Sampling feature is currently only available for the following SDKs:
- Python: 1.7.2 or later
- Apple: 7.23.0 or later
- Android: 6.5.0 or later
- React Native: 4.3.0 or later
- Dart and Flutter: 6.11.0 or later
- PHP: 3.9.0 or later
- Laravel: 3.0.0 or later
- Symfony: 4.4.0 or later
- Ruby: 5.5.0 or later
- Java: 6.5.0 or later
- .NET: 3.22.0 or later
- Go: 0.16.0 or later
If your application relies on any Sentry SDK that isn't specified above, then you won’t be able to use Sentry's Dynamic Sampling.
Once you’ve confirmed that your application only relies on supported SDKs, then the next step is to update them to the specified version or higher. Check out the migration documentation for the SDKs you’re using to learn everything you need to know to get up and running again with the latest Sentry features.
While we do our best to provide you with the most useful transaction data, our Dynamic Sampling feature allows you to turn the priorities that we apply to your data retention on or off:
Because every project is different, you can set these toggles differently for different projects. For example, you may have a project where the retaining transactions from the latest release is not a priority for you.
By default, these toggles are all enabled so that Sentry's dynamic sampling priorities are applied to your data.
Our dynamic sampling works best when you send us as much data as you can (ideally 100%). As you purchase more transaction volume, however, your per-transaction pricing goes down accordingly. Update your transaction sample rate in the SDK by setting the tracesSampleRate.