Sentry isn't capturing any errors (trying to upgrade from Raven with simple initialization)

[armanelli]

Hello! I've been trying for a couple of days to make this work and couldn't figure it out yet :(

We have a ReactJS project, that is currently using an old version of Raven package, and it works normally. Now I'm locally changing to use the latest version of Sentry (7.38.0 as of now), to later deploy to our staging and production environments as well.

I've

• Removed old raven packages
• Added "@sentry/react" and "@sentry/tracing" packages
• Created initialization file with a simple Sentry.init code
• Added a button that calls an undefined function to simulate an error

I'm trying to keep the initialization simple at first just to make it work and add more details later.

Here's what my initialization looks like:

// sentry.js file

import * as Sentry from '@sentry/react';
import { BrowserTracing } from '@sentry/tracing';

const {
  REACT_APP_SENTRY_URL,
  REACT_APP_REPO_NAME,
  REACT_APP_BRANCH,
} = process.env;

Sentry.init({
  dsn: REACT_APP_SENTRY_URL,
  integrations: [new BrowserTracing()],
  tracesSampleRate: 1.0,
  environment: 'staging',
  beforeSend(event) {
    return {
      ...event,
      contexts: {
        ...event.contexts,
        state: {},
      },
      breadcrumbs: [],
    };
  }
});

Sentry.configureScope(scope => {
  scope.setTag('repo', REACT_APP_REPO_NAME);
  scope.setTag('branch', REACT_APP_BRANCH);
});

I can see the network requests after throwing an error, they all respond with 200 status code, but no errors appear on the project dashboard.

Does anyone come across this when upgrading from Raven and have some ideas? Thanks!

[AbhiPrasad]

Hey @armanelli - are you running self-hosted? Our v7 SDKs require a min version of 20.6.0: https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md#700

Otherwise super strange that sentry is not sending any errors. If you try with a sample https://codesandbox.io app, does the same still apply?

[armanelli]

Hello @AbhiPrasad, it was a setting that I didn't know of that was turned on, so it was my mistake, I will leave it here in case anyone needs to know as well.

Turns out that since our Sentry dashboard is managed by another teammate from back-end/DevOps, we had a setting Inboud Data Filters turned on, that filters out errors from localhost.

So I originally catch this when I created another Sentry project and DSN to test, and later I spotted this difference in the Project Settings page.

So this should be turned off when you need to trigger errors from localhost.

(Or to be more easily and avoid your teammates receiving a bunch of alerts from Sentry, it's easier to create a temp project to test the Tags, Contexts, etc)

Anyways, thank you for your help!