Filtering

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 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.

Filtering Error Events

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

Using beforeSend

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

await SentryFlutter.init((options) {
  options.beforeSend = (event, hint) {
    return event.copyWith(serverName: null); // Don't send server names.
  };
});

Note also that breadcrumbs can be filtered, as discussed in our Breadcrumbs documentation.

Event Hints

The beforeSend callback is passed both the event and a second argument, hint, that holds one or more hints.

Typically, a hint holds the original exception so that additional data can be extracted or grouping is affected. In this example, the fingerprint is forced to a common value if an exception of a certain type has been caught:

await SentryFlutter.init((options) {
  options.beforeSend = (event, hint) {
    return hint is MyHint ? null : event;
  };
});

When the SDK creates an event or breadcrumb for transmission, that transmission is typically created from some sort of source object. For instance, an error event is typically created from a log record or exception instance. For better customization, SDKs send these objects to certain callbacks (beforeSend, beforeBreadcrumb or the event processor system in the SDK).

Using Hints

Hints are available in two places:

1. beforeSend / beforeBreadcrumb
2. eventProcessors

Event and breadcrumb hints are objects containing various information used to put together an event or a breadcrumb. Typically hints hold the original exception so that additional data can be extracted or grouping can be affected.

For events, hints contain properties such as event_id, originalException, syntheticException (used internally to generate cleaner stack trace), and any other arbitrary data that you attach.

For breadcrumbs, the use of hints is implementation dependent. For XHR requests, the hint contains the xhr object itself; for user interactions the hint contains the DOM element and event name and so forth.

await SentryFlutter.init((options) {
  options.beforeSend = (event, hint) {
    if (event.throwable is DatabaseException) {
      event = event.copyWith(fingerprint: ['database-connection-error']);
    }
    return event;
  };
});

Hints for Events

originalException

The original exception that caused the Sentry SDK to create the event. This is useful for changing how the Sentry SDK groups events or to extract additional information.

syntheticException

When a string or a non-error object is raised, Sentry creates a synthetic exception so you can get a basic stack trace. This exception is stored here for further data extraction.

Hints for Breadcrumbs

event

For breadcrumbs created from browser events, the Sentry SDK often supplies the event to the breadcrumb as a hint. This can be used to extract data from the target DOM element into a breadcrumb, for example.

level / input

For breadcrumbs created from console log interceptions. This holds the original console log level and the original input data to the log function.

response / input

For breadcrumbs created from HTTP requests. This holds the response object (from the fetch API) and the input parameters to the fetch function.

request / response / event

For breadcrumbs created from HTTP requests. This holds the request and response object (from the node HTTP API) as well as the node event (response or error).

xhr

For breadcrumbs created from HTTP requests made using the legacy XMLHttpRequest API. This holds the original xhr object.

Using allowUrls (Web only)

Based on the URL, you can narrow down whether events should be sent to Sentry. Using allowUrls, events are only sent if the URL matches the pattern specified in allowUrls. allowUrls accepts regular expressions.

If used on a platform other than Web, this setting will be ignored.

await SentryFlutter.init((options) {
  options.allowUrls = ["^https://sentry.com.*\$", "my-custom-domain"];
});

Using denyUrls (Web only)

You can exclude events sent to Sentry based on the URL. Using denyUrls, events are ignored if the URL matches the pattern specified in denyUrls. denyUrls accepts regular expressions.

When used in combination with allowUrls, you can block specific subdomains of the domains listed in allowUrls.

If used on a platform other than Web, this setting will be ignored.

await SentryFlutter.init((options) {
  options.denyUrls = ["^.*ends-with-this\$", "denied-url"];
});

Filtering Transaction Events

To prevent certain transactions from being reported to Sentry, use the tracesSampler or beforeSendTransaction configuration option, which allows you to provide a function to evaluate the current transaction and drop it if it's not one you want.

Using tracesSampler

Note: The tracesSampler and tracesSampleRate config options are mutually exclusive. If you define a tracesSampler 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.

In its simplest form, used just for filtering the transaction, it looks like this:

await SentryFlutter.init((options) {
  // Determine traces sample rate based on the sampling context
  options.tracesSampler = (samplingContext) {
    final ctx = samplingContext.customSamplingContext;
    // If this is the continuation of a trace, just use that decision (rate controlled by the caller).
    final parentSampled =
        samplingContext.transactionContext.parentSampled;
    if (parentSampled != null) {
      return parentSampled ? 1.0 : 0.0;
    }

    if (/* make a decision based on `samplingContext` */) {
      // Drop this transaction, by setting its sample rate to 0%
      return 0.0;
    } else if (/* ... */) {
      // Override sample rate for other cases (replaces `options.TracesSampleRate`)
      return 0.1;
    }
    // Can return `null` to fallback to the rate configured by `options.tracesSampleRate`
    return null;
  };
});

It also allows you to sample different transactions at different rates.

If the transaction currently being processed has a parent transaction (from an upstream service calling this service), the parent (upstream) sampling decision will always be included in the sampling context data, so that your tracesSampler can choose whether and when to inherit that decision. In most cases, inheritance is the right choice, to avoid breaking distributed traces. A broken trace will not include all your services. See Inheriting the parent sampling decision to learn more.

Learn more about configuring the sample rate.