-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(dynamic-sampling): organization settings #11791
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
Changes from 7 commits
714bbef
4092b56
cf6ed25
c9eab8e
0559a31
778beb6
c73f242
3a07833
a872516
aa9d35c
0405349
a1a33fb
4795538
797efb9
d5cae09
1b212fc
70990f8
11ba516
be109c7
6e2c87e
aba7b8b
f334b04
3c7a5c6
df915d9
8307844
81e1f08
8aa5890
60ac005
0dc606b
45ad919
5550bb0
704ab13
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,47 @@ | ||
| --- | ||
| title: Retention Priorities | ||
| sidebar_order: 130 | ||
| description: "Learn how Sentry determines retention priorities and how to update them." | ||
| title: Dynamic Sampling | ||
| sidebar_order: 30 | ||
| description: "Learn how to make your billing quota go farther with Sentry's Dynamic Sampling." | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| High-volume projects that generate many events can quickly consume a large portion of your billing quota, leaving less room for other projects and decreasing visibility across them. | ||
|
|
||
| With high-volume projects, you'll often see many similar events, which can be redundant and less helpful for debugging. But with Dynamic Sampling, you can maximize your quota by adjusting sample rates based on each project’s event volume. The sample rate is a percentage from 0% (no events passed) to 100% (all events passed), that can be tailored to each project’s needs. | ||
|
|
||
| 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. | ||
constantinius marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|  | ||
|
|
||
| ## Modes | ||
|
|
||
| You can choose between two Dynamic Sampling modes for your organization: manual or automatic. | ||
|
|
||
| * **`automatic`** (default): In automatic mode, the sample rate for each project is set automatically based on relative project volume, so events fit within your organization’s billing quota. This boosts visibility into lower-volume projects. To account for any changes in event volume, sample rates are recalibrated on a regular basis. Automatic mode overrides any manually-set project sample rates. | ||
|
|
||
| * **`manual`**: If you want to set the exact sample rate for each project in your organization yourself, choose manual mode. Note, that in this mode, there is no automatic recalibration. | ||
|
|
||
|
|
||
| []: # (TODO: Rename AM3 with the actual user-facing name.) | ||
|
|
||
| <Note> | ||
|
|
||
| Please note that these Dynamic Sampling modes are only available for customers on the AM3 platform. | ||
|
||
|
|
||
| </Note> | ||
|
|
||
|
|
||
| ## Differences to Sampling in the Sentry SDKs | ||
|
|
||
| Dynamic Sampling is different from the sampling that you can configure in the Sentry SDKs. The SDK sampling rate is applied before events are sent to Sentry, while Dynamic Sampling is applied after events are received by Sentry. This means that Dynamic Sampling can be used to adjust the sample rate for events that have already been sent to Sentry and only take into account the volume of events that have been received by Sentry. | ||
|
|
||
| Also in contrast to the Dynamic Sampling, the SDK sample rate is never dynamically adjusted. | ||
|
||
|
|
||
| ## Retention Priorities | ||
|
|
||
|
|
||
|
|
||
| <Note> | ||
|
|
||
| Retention priorities are only available on the latest version of our plans, starting from 1M reserved transactions. Anyone in your org with owner or billing-level permissions can update your plan by going to Settings > Subscription, and clicking the "Manage Subscription" button. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.