Node.jsInboundFilters
Import name: Sentry.inboundFiltersIntegration
This integration is enabled by default. If you'd like to modify your default integrations, read this.
This integration allows you to ignore specific errors based on the type, message, or URLs in a given exception.
By default, it'll ignore errors that start with Script error or Javascript error: Script error.
To configure this integration, use the ignoreErrors, ignoreTransactions, denyUrls, and allowUrls SDK options directly. For example:
Sentry.init({
ignoreErrors: ["ignore-this-error"],
});
Remember to pass these options to the root Sentry.init call, not the integration!
Type: (string|RegExp)[]
A list of strings or regex patterns that match error messages that shouldn't be sent to Sentry. Messages that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, all errors are sent.
Type: (string|RegExp)[]
A list of strings or regex patterns that match transaction names that shouldn't be sent to Sentry. Transactions that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, transactions spanning typical API health check requests are filtered out.
Type: (string|RegExp)[]
A list of strings or regex patterns that match error URLs that should not be sent to Sentry. Errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will not be sent. As a result, if you add 'foo.com' to the list, it will also match on https://bar.com/myfile/foo.com. Keep in mind that this only applies for captured exceptions, not raw message events. By default, all errors are sent.
Type: (string|RegExp)[]
A list of strings or regex patterns that match error URLs which should exclusively be sent to Sentry. If you use this option, only errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will be sent. As a result, if you add 'foo.com' to it, it will also match on https://bar.com/myfile/foo.com. Keep in mind that this only applies for captured exceptions, not raw message events. By default, all errors are sent.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
