Sentry.captureException not appearing on Sentry

[dhruvg]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

7.73.0

Framework Version

No response

Link to Sentry event

[redacted]

Reproduction Example/SDK Setup

Sentry.init({
  dsn: process.env.NODE_ENV === 'production' && SENTRY_SERVER_DSN,
  release: process.env.RELEASE_VERSION,
  environment: process.env.NODE_ENV,
});

Steps to Reproduce

console.log(`Sending to Sentry...`);
Sentry.captureException(error, { extra });

In my logs I see:

Mar 23 14:33:18 ip-172-30-1-243 web[3564377]: [23/03/2025 14:33:18.851] [LOG]    Sending to Sentry...

Expected Result

I expect every log of Sending to Sentry... to have a corresponding error event on my Sentry dashboard.

Actual Result

Hundreds of such errors have been logged so far, but only 4 events have made it to Sentry.

[lforst]

Hi, if you go to the Stats page of your organization you can see why errors are getting dropped by Sentry. A lot of them are being dropped because Sentry detected them coming from web-crawler traffic. How are you testing your errors?

[lforst]

The web crawler detection kicks in when the user agent matches one of these regexes: https://github.com/getsentry/relay/blob/master/relay-filter/src/web_crawlers.rs#L8-L39

[dhruvg]

Thanks, that clears things up. The error was indeed mostly triggered by web crawler traffic. The ones that got through weren't -- makes sense.