Skip to content

Commit cf6ed25

Browse files
fix(dynamic-sampling): use suggestions
Co-authored-by: Liza Mock <[email protected]>
1 parent 4092b56 commit cf6ed25

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

docs/organization/dynamic-sampling/index.mdx

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,20 @@ description: "Dynamic Sampling allows users make the most of their quota by dyna
66

77
## Overview
88

9-
When you are dealing with projects that generate high volumes of events, your quotas might be consumed quickly. Additionally, high volume projects will eat up a bigger portion of it, leaving less for other projects.
9+
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.
10+
11+
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.
12+
13+
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.
14+
15+
16+
17+
18+
19+
1020

11-
Many events may be redundant or not useful for debugging. Dynamic Sampling allows you to make the most of your quota by dynamically determining a target sample rate from the given volumes of the projects.
1221

13-
When you use Dynamic Sampling, your projects within an organization are sampled according to their event volumes of the past period. Higher volume projects are sampled at a lower rate, while lower volume projects are sampled at a higher rate or not sampled at all. This way, each project has a similar set of significant events to investigate, granting more visibility to the spans that actually matter.
1422

15-
A sample rate is a percentage from 0% (no events are passed on) to 100% (all events are passed on).
1623

1724
## Modes
1825

0 commit comments

Comments
 (0)