Skip to content

Commit 270ac73

Browse files
committed
remove sample rate section
1 parent 0cc0910 commit 270ac73

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

src/docs/product/accounts/quotas/manage-transaction-quota.mdx

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -138,12 +138,6 @@ If you have a rogue client, Sentry supports blocking an IP from sending data. Na
138138

139139
If you discover a problematic release causing excessive noise, Sentry supports ignoring all events and attachments from that release. Navigate to **[Project] > Settings > Inbound Filters**, then add the release to the "Releases" field.
140140

141-
## 3. SDK Sample Rate
142-
143-
If a sample rate is defined for the SDK, the SDK evaluates whether this event should be sent as a representative fraction of events. Setting a sample rate is [documented for each SDK](/platform-redirect/?next=/configuration/sampling/).
144-
145-
The SDK sample rate is not dynamic; changing it requires re-deployment. Also, keep in mind that setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project may better suit your needs.
146-
147-
## 4. SDK Configuration: Tracing Options {#2-sdk-configuration-tracing-options}
141+
## 3. SDK Configuration: Tracing Options {#2-sdk-configuration-tracing-options}
148142

149143
When you configure your the SDK, you can control the number of transactions that are sent to Sentry by setting the [tracing options](/platform-redirect/?next=/configuration/options/%23tracing-options). You can also set up [custom instrumentation](/platform-redirect/?next=/performance/instrumentation/custom-instrumentation/) for performance monitoring to capture certain types of transactions.

0 commit comments

Comments
 (0)