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
To prevent certain transactions from being reported to Sentry, use the <PlatformIdentifiername="traces-sampler" /> or <PlatformIdentifiername="before-transaction" /> configuration option, which allows you to provide a function to evaluate the current transaction and drop it if it's not one you want.
88
+
## Using Sampling to Filter Transaction Events
89
89
90
-
### Using <PlatformIdentifiername="traces-sampler" />
90
+
To prevent certain transactions from being reported to Sentry, use the <PlatformIdentifiername="traces-sampler" /> configuration option, which allows you to provide a function to evaluate the current transaction and drop it if it's not one you want. (It also allows you to sample different transactions at different rates.)
91
91
92
92
**Note:** The <PlatformIdentifiername="traces-sampler" /> and <PlatformIdentifiername="traces-sample-rate" /> config options are mutually exclusive. If you define a <PlatformIdentifiername="traces-sampler" /> to filter out certain transactions, you must also handle the case of non-filtered transactions by returning the rate at which you'd like them sampled.
93
93
94
94
In its simplest form, used just for filtering the transaction, it looks like this:
0 commit comments