You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/organization/dynamic-sampling/index.mdx
+14-15
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,11 @@ This process is applied directly on Sentry's servers, which allows you to config
14
14
15
15
By analyzing incoming traffic patterns, Dynamic Sampling is able to tailor its decisions to both the actual traffic volume as well as the content of accepted spans. For more details, check out the [Dynamic Sampling Priorities](#dynamic-sampling-priorities) section.
16
16
17
+
<Note>
18
+
Dynamic Sampling is available for customers on our latest Enterprise plans,
@@ -40,16 +45,10 @@ In this section you'll learn how to use Dynamic Sampling in your organization.
40
45
41
46
### Modes
42
47
43
-
If you prefer not to set sample rates manually, Sentry can do it for you. You just have to set a global sample rate for your organization and Sentry will then automatically balance the sample rates across projects, giving priority to factors like low-volume endpoints and new releases. If you want more fine-grainedcontrol, you can customize data retention by setting individual sample rates for specific projects.
48
+
If you prefer not to set sample rates manually, Sentry can do it for you. You just have to set a global sample rate for your organization and Sentry will then automatically balance the sample rates across projects, giving priority to factors like low-volume endpoints and new releases. If you want more fine-grained control, you can customize data retention by setting individual sample rates for specific projects.
44
49
45
50
We recommend using simple mode in most cases for its convenience, because it automatically adjusts projects based on their traffic.
46
51
47
-
<Note>
48
-
49
-
Dynamic Sampling modes are only available for customers on our latest plans, starting June, 2024.
50
-
51
-
</Note>
52
-
53
52
### Simple Mode
54
53
55
54
In simple mode, you set a global target sample rate for your entire organization, which determines how much incoming traffic should be stored across all your projects. Dynamic Sampling then distributes this sample rate across your projects automatically. Sample rates are adjusted continuously to account for changes in event volume over time.
@@ -71,7 +70,10 @@ The [project preview](https://sentry.io/orgredirect/organizations/:orgslug/setti
71
70
Because project rates continuously change, we recommend that you choose the 24-hour preview to get a more accurate view of your current sample rates for real-time analysis. We recommend the 30-day preview for seeing average sample rates in your billing cycle for long-term planning.
72
71
73
72
<Note>
74
-
If you switch from advanced to simple mode, the recalibration process will start immediatly and the per-project sample rates will be reset to the calculated values. There's no way to restore the manually configured project sample rates once you've switched to simple mode.
73
+
If you switch from advanced to simple mode, the recalibration process will
74
+
start immediatly and the per-project sample rates will be reset to the
75
+
calculated values. There's no way to restore the manually configured project
76
+
sample rates once you've switched to simple mode.
75
77
</Note>
76
78
77
79
### Advanced Mode
@@ -92,12 +94,10 @@ For example, if a trace starts in your frontend application, the sample rate you
92
94
93
95
If you navigate to the [project preview](https://sentry.io/orgredirect/organizations/:orgslug/settings/dynamic-sampling/) table, you'll see the number of sent spans next to the origin project where the trace started. This includes any spans from propogated traces in other projects that are connected to the origin project. This gives you a direct view of how many spans will be affected by the sample rates you configure. To see the span counts broken down by the project they belong to, click the expand icon to the left of each project in the preview.
94
96
95
-
96
97
{/* TODO: replace with custom graphic */}
97
98
98
99
{/*  */}
99
100
100
-
101
101
## SDK versus Dynamic Sampling
102
102
103
103
SDK sampling happens at the application level, before events are sent to Sentry. It filters events by sending only a set percentage, reducing data volume and instrumentation overhead. This helps with managing high event volumes directly at the source.
@@ -121,10 +121,10 @@ SDK sampling uses a static rate set in the SDK configuration. It’s ideal for o
121
121
To give Sentry the fullest, most accurate picture of your application’s health, we recommend sending us 100% of your transactions. You can do this by setting your [tracesSampleRate](/platform-redirect/?next=/performance/) to 1.0. If this isn't feasible for your organization, set a lower value, or switch to sampling selectively by using the [tracesSampler](/platform-redirect/?next=/performance/) to filter your transactions based on contextual data. Note, that when calculating throughput, transaction-metering is based on received, not stored transactions.
122
122
123
123
<Note>
124
-
Changes to your SDK sampling configuration may affect your
125
-
quota. If you increase your SDK sampling rate, you'll also be increasing the
126
-
volume of transactions you send to Sentry. This may require that you adjust
127
-
your transaction quota.
124
+
Changes to your SDK sampling configuration may affect your quota. If you
125
+
increase your SDK sampling rate, you'll also be increasing the volume of
126
+
transactions you send to Sentry. This may require that you adjust your
127
+
transaction quota.
128
128
</Note>
129
129
130
130
You can use both Dynamic 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 event volume received by Sentry.
@@ -197,7 +197,6 @@ It's also possible to create a rule from the Transaction Summary page in Perform
197
197
198
198

199
199
200
-
201
200
### Deprioritized Transactions
202
201
203
202
Sentry automatically deprioritizes the following transactions:
0 commit comments