Default Integrations

System integrations are integrations enabled by default that integrate into the standard library or the interpreter itself. They are documented so you can see what they do and that they can be disabled if they cause issues. To disable system integrations set defaultIntegrations: false when calling init(). To override their settings, provide a new instance with your config to integrations option, for example to turn off browser capturing console calls integrations: [new Sentry.Integrations.Breadcrumbs({ console: false })].

Core

Dedupe

Import name: Sentry.Integrations.Dedupe

This integration deduplicates certain events. This is enabled by default and should not be disabled except in rare circumstances. Disabling this integration for instance will cause duplicate error logging.

FunctionToString

Import name: Sentry.Integrations.FunctionToString

This integration allows SDK to provide original functions and method names, even when they are wrapped by our error or breadcrumbs handlers.

InboundFilters

Import name: Sentry.Integrations.InboundFilter

This integration allows developers to ignore specific errors based on the type or message, as well as blacklist/whitelist urls which exception originates from.

To configure it, use ignoreErrors, blacklistUrls and whitelistUrls SDK options directly.

Browser specific

Import name: Sentry.Integrations.Breadcrumbs

This integration wrap native APIs to capture breadcrumbs. By default, all APIs are wrapped.

Available options:

{
  beacon: boolean;
  console: boolean;
  dom: boolean;
  fetch: boolean;
  history: boolean;
  sentry: boolean;
  xhr: boolean;
}

GlobalHandlers

Import name: Sentry.Integrations.GlobalHandlers

This integration attaches global handlers to capture uncaught exceptions and unhandled rejections.

Available options:

{
  onerror: boolean;
  onunhandledrejection: boolean;
}

LinkedErrors

Import name: Sentry.Integrations.LinkedErrors

This integration allows to configure linked errors. They’ll be recursively read up to a specified limit and lookup will be performed by a specific key. By default, limit is set to 5 and key used is cause.

Available options:

{
  key: string;
  limit: number;
}

ReportingObserver

Import name: Sentry.Integrations.ReportingObserver

This integration hooks into ReportingObserver API and sends captured events through to Sentry. Can be configured to handle only specific issue types.

Available options:

{
  types: <'crash'|'deprecation'|'intervention'>[];
}

TryCatch

Import name: Sentry.Integrations.TryCatch

This integration wraps native time and events APIs (setTimeout, setInterval, requestAnimationFrame, addEventListener/removeEventListener) in try/catch blocks to handle async exceptions.

UserAgent

Import name: Sentry.Integrations.UserAgent

This integration attaches user-agent information to the event, which allows us to correctly catalogue and tag them with specific OS, Browser and version informations.