# Filtering | Sentry for Godot Engine

When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume.

The Sentry SDKs have several configuration options to help you filter out events.

We also offer [Inbound Filters](https://docs.sentry.io/concepts/data-management/filtering.md) to filter events in sentry.io. We recommend filtering at the client level though, because it removes the overhead of sending events you don't actually want. Learn more about the [fields available in an event](https://develop.sentry.dev/sdk/data-model/event-payloads.md).

## [Filtering Error Events](https://docs.sentry.io/.md#filtering-error-events)

Configure your SDK to filter error events by using the `before_send` callback method and configuring, enabling, or disabling integrations.

### [Using `before_send`](https://docs.sentry.io/.md#using-before-send)

All Sentry SDKs support the `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. `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.

```GDScript
extends SentryConfiguration
## Tip: Assign configuration script in the Project Settings.

func _configure(options: SentryOptions):
	options.before_send = _before_send

func _before_send(event: SentryEvent) -> SentryEvent:
	if event.environment == "debug":
		# Discard event if running in a debug build.
		return null
	if event.message.contains("Bruno"):
		# Remove sensitive information from the event.
		event.message = event.message.replace("Bruno", "REDACTED")
	return event
```

Note also that breadcrumbs can be filtered, as discussed in [our Breadcrumbs documentation](https://docs.sentry.io/product/error-monitoring/breadcrumbs.md).
