Nitro: Errors are reported twice

[MickL]

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/nitro

SDK Version

11.1.0

Framework Version

11.1.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Handler /routes/sentry.ts from the docs:

import { defineHandler } from 'nitro/h3';

export default defineHandler(() => {
  throw new Error('Sentry error tracing is working!');
});

Expected Result

• Should report one error to Sentry
• Specific errors like 401 should not be reported to Sentry

Actual Result

• Errors show up twice in Sentry, once as Error and once as HttpError
• Specific errors like 401 are reported to Sentry (once) as HttpError

Additional Context

Found that @sentry/nitro reports errors from two places: The error hook (which filters 4xx) and the h3 tracing channel (which doesn't), causing duplicate reports and letting the 401 slip through unfiltered.

Priority

Critical ?

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear-code]

JS-3861

[MickL]

Workaround until fixed, in instrument.mjs:

Sentry.init({
  dsn: process.env.NITRO_SENTRY_DSN,
  tracesSampleRate: 1,
  beforeSend: (event) => {
    // TODO: Remove, workaround until this is fixed: https://github.com/getsentry/sentry-javascript/issues/24939  
    if (event.exception?.values?.some(({ mechanism }) => mechanism?.type === 'auto.http.nitro.onTraceError')) {
      return null;
    }

    return event;
  },
});

This drops everything from the tracing channel (onTraceError) and keeps everything from Nitro's error hook (captureErrorHook), which is the path that skips 3xx/4xx.

[nicohrubec]

Hey, thanks for raising! I just merged a fix so this should be working correctly in the next release.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #24952, which was included in the 11.3.0 release.