Pluggable Integrations

Pluggable integrations are integrations that can be additionally enabled, to provide some very specific features. They are documented so you can see what they do and that they can be enabled. To enable pluggable integrations, provide a new instance with your config to integrations option, for example integrations: [new Sentry.Integrations.Modules()].



Import name: Sentry.Integrations.Debug

This integration allows you to easily inspect the content of the processed event, that will be passed to beforeSend and effectively send to the Sentry.

Available options:

  debugger: boolean; // trigger DevTools debugger instead of using console.log
  stringify: boolean; // stringify event before passing it to console.log


Import name: Sentry.Integrations.RewriteFrames

This integration allows you to apply transformation to each frame of the stack trace. In the simple scenario, it can be used to change name of the file frame originates from, or can be fed with iteratee function, to apply any arbitrary transformation.

Available options:

  root: string; // root path that will be appended to the basename of the current frame's url
  iteratee: (frame) => frame); // function that take the frame, apply any transformation on it and returns it back

Node specific


Import name: Sentry.Integrations.Modules

This integration fetches names of all currently installed node modules and attaches the list to the event. Once fetched, the list will be cached for later reuse.


Import name: Sentry.Integrations.Transaction

This integration tries to extract usable transaction name, that will be used to distinguish the event from the rest. It walks through all stack trace frames and reads first in-app frame’s module and function name.