Skip to content

Commit a872516

Browse files
committed
docs(dynamic-sampling): better distinction between SDK and dynamic sampling
improve description of recalibration algorithm
1 parent 3a07833 commit a872516

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

docs/organization/dynamic-sampling/index.mdx

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,10 @@ With high-volume projects, you'll often see many similar events, which can be re
1212

1313
When you use Dynamic Sampling, projects in your organization are sampled based on their recent event volumes. High-volume projects are sampled at lower rates while lower-volume projects are sampled at higher rates or not sampled at all, based on your recent event data. This makes it possible for each project to retain a meaningful set of key events, improving visibility into all projects regardless of their size.
1414

15+
The sample rate is dynamically (re-)calibrated in regular intervals to ensure that the sample rate is always optimized generated traffic, hence the name Dynamic Sampling.
16+
17+
For the recalibration, a short sliding window algorithm is used to help with seasonal traffic patterns. Weekends, holidays, night times will likely reduce the event volume, and thus different sample rates are needed to keep the same visibility.
18+
1519
![The dynamic sampling mode and target sample rate setting.](./img/mode-and-target-sample-rate.png)
1620

1721
## Modes
@@ -38,6 +42,16 @@ Dynamic Sampling is different from the sampling that you can configure in the Se
3842

3943
Also in contrast to the Dynamic Sampling, the SDK sample rate is never dynamically adjusted.
4044

45+
### When to Use Dynamic Sampling vs. SDK Sampling
46+
47+
The biggest benefit of Dynamic Sampling is that, as the name implies, it's dynamic. This means that the sample rate is adjusted based on the volume of events that have been received by Sentry. This makes it a great choice for organizations that have a mix of high- and low-volume projects, as it allows you to maximize your quota by adjusting the sample rate based on each project’s event volume.
48+
49+
On the other hand, the SDK sample rate is static and set by you in the SDK configuration. This makes it a good choice for organizations that have a consistent event volume and want to ensure that only a certain percentage of events are sent to Sentry.
50+
51+
### Combine Dynamic Sampling with SDK Sampling
52+
53+
You can use both Dynamic Sampling and SDK Sampling together to further optimize your event volume for your specific use case. For example, you can set a low SDK sample rate to ensure that only a certain percentage of events are sent to Sentry, and then use Dynamic Sampling to adjust the sample rate based on the volume of events that have been received by Sentry.
54+
4155
## Dynamic Sampling Priorities
4256

4357
<Note>

0 commit comments

Comments
 (0)