Skip to content

Commit 577df1a

Browse files
JonasBalizokm
andauthored
Update docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx
Co-authored-by: Liza Mock <[email protected]>
1 parent c037b0c commit 577df1a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ We recommend that you call the `startProfiling` method right after the Sentry SD
3434

3535
## Choosing Between Transaction and Continuous Profiling Mode
3636

37-
Unfortunately, at this time it's not possible to use both profiling modes at the same time as they're mutually exclusive. The mode you intend to use will depend on the SDK initialization arguments, profiling mode will have to be selected when the Sentry SDK is first initialized.
37+
Currently, it's not possible to use both profiling modes at the same time because they're mutually exclusive. You'll have to choose the SDK initialization arguments for the mode that works best for you when you first initialize the Sentry SDK.
3838

3939
To enable continuous profiling, you have to make sure that neither `profileSampleRate` nor `profilesSampler` are set as the values of the `Sentry.Init` call. If either of those values are set, the SDK will default to transaction-based profiling. When the SDK is configured for continuous profiling, the top level calls to start profiles will enable calls to the profiler. If the SDK is configured for transaction-based profiling, these calls will void and not trigger the profiler.
4040

0 commit comments

Comments
 (0)