From 76a44a937612860dfcf5cc304a9459dcf82f58e9 Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Mon, 22 Apr 2024 10:21:42 +0000 Subject: [PATCH] ref(nextjs): Remove unnecessary logic to filter symbolification/sentry spans --- packages/nextjs/src/server/index.ts | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/packages/nextjs/src/server/index.ts b/packages/nextjs/src/server/index.ts index b093d9bd2e97..a67677d9a1a5 100644 --- a/packages/nextjs/src/server/index.ts +++ b/packages/nextjs/src/server/index.ts @@ -151,29 +151,6 @@ export function init(options: NodeOptions): void { ), ); - // TODO(v8): Remove this because we have `suppressTracing` - addEventProcessor( - Object.assign( - (event => { - if (event.type === 'transaction') { - event.spans = event.spans?.filter(span => { - // Filter out spans for Sentry event sends - const httpTargetAttribute: unknown = span.data?.['http.target']; - if (typeof httpTargetAttribute === 'string') { - // TODO: Find a more robust matching logic - We likely want to use the OTEL SDK's `suppressTracing` in our transport, if we end up using it, we can delete this filtering logic here. - return !httpTargetAttribute.includes('sentry_client') && !httpTargetAttribute.includes('sentry_key'); - } - - return true; - }); - } - - return event; - }) satisfies EventProcessor, - { id: 'NextFilterSentrySpans' }, - ), - ); - if (process.env.NODE_ENV === 'development') { addEventProcessor(devErrorSymbolicationEventProcessor); }