Skip to content

Commit b9dc450

Browse files
sentrivanalizokm
andauthored
Make it clearer that before_send can drop events (#8300)
Co-authored-by: Liza Mock <liza.mock@sentry.io>
1 parent 9569bb2 commit b9dc450

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/platforms/common/configuration/filtering.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Configure your SDK to filter error events by using the <PlatformIdentifier name=
1818

1919
### Using <PlatformIdentifier name="before-send" />
2020

21-
All Sentry SDKs support the <PlatformIdentifier name="before-send" /> callback method. <PlatformIdentifier name="before-send" /> is called immediately before the event is sent to the server, so it’s the final place where you can edit its data. It receives the event object as a parameter, so you can use that to modify the event’s data or drop it completely (by returning `null`) based on custom logic and the data available on the event.
21+
All Sentry SDKs support the <PlatformIdentifier name="before-send" /> callback method. Because it's called immediately before the event is sent to the server, this is your last chance to decide not to send data or to edit it. <PlatformIdentifier name="before-send" /> receives the event object as a parameter, which you can use to either modify the event’s data or drop it completely by returning `null`, based on custom logic and the data available on the event.
2222

2323
<PlatformContent includePath="configuration/before-send" />
2424

0 commit comments

Comments
 (0)