How to disable Sentry again at runtime?

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Description

We allow to enable or disable error reporting in our browser extension (which is needed for GDPR). A browser extensions background script is long-running (doesn’t re-run at page reloads), so when error reporting is disabled, we need to disable Sentry after it was already enabled with Sentry.init(). I see there is Sentry.init({ enabled: false }) but it doesn’t look legal to call Sentry.init() twice. How can I disable Sentry after it was enabled before, at runtime?

[felixfbecker]

As described in the issue description, we need to allow users to opt in and out of error reporting for privacy reasons. Anything that is unclear? Happy to provide more info but not sure what you are looking for

[kamilogorek]

In Raven I think you had shouldSendCallback to toggle reporting

Sentry.init({
  beforeSend(event) {
    if (shouldSendEvent) return event;
    return null;
  }
});

Any updates on providing the Sentry.setEnabled(boolean) to toggle error reports on/off?

What’s your use-case specifically? It’s already possible to conditionally drop and/or enable/disable sdk.