Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit f294ede

Browse files
sl0thentr0pyszokeasaurusrex
andauthoredMar 18, 2025··
Update develop-docs/sdk/overview.mdx
Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>
1 parent 01d43e5 commit f294ede

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed
 

‎develop-docs/sdk/overview.mdx

+1-2
Original file line numberDiff line numberDiff line change
@@ -336,8 +336,7 @@ We try our best to make our SDKs error-free. We are an exception monitoring serv
336336
and throwing our own exceptions is awkward. However, if our SDKs do throw exceptions, we have to make
337337
sure we swallow them gracefully and emit an error level log describing the failure.
338338

339-
As a **design principle**, we never capture Sentry events for exceptions happening within our SDKs.
340-
This includes user-defined callbacks and hooks such as `before_send`, `traces_sampler` and so on.
339+
As a **design principle**, we never capture Sentry events for exceptions happening within our SDKs, including within user-defined callbacks and hooks such as `before_send` or `traces_sampler`.
341340

342341
The main justification for this is that we are already in an event capturing flow where the scope has been applied
343342
and capturing another event at that point in the lifecycle would lead to undefined behavior. In the worst case,

0 commit comments

Comments
 (0)
Please sign in to comment.