You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today @sentry/node (and everything built on it) always installs an OpenTelemetry tracer provider + context strategy via initOpenTelemetry. For v11 we want to flip the default: most SDKs should run without a tracer provider (core startSpan APIs + an AsyncLocalStorage context strategy for scope isolation, i.e. the old node-core/light model), and only the SDKs that genuinely need OTel span pickup (Next.js, SvelteKit) should default to the full tracer-provider setup.
Users on any SDK must still be able to opt into a tracer provider when they want OTel spans surfaced in Sentry. We need to decide whether to introduce a new flag or reuse/rename an existing one, and settle the default per SDK.
Considerations
Existing related options: skipOpenTelemetrySetup, openTelemetryBasicTracerProvider, openTelemetrySpanProcessors. Prefer reusing/reframing over adding a fourth overlapping flag if we can.
Default matrix: node / bun / aws-serverless / google-cloud-serverless / etc. → no tracer provider; nextjs / sveltekit → tracer provider. Confirm the full list.
Requires an AsyncLocalStorage-based async context strategy available in @sentry/node (the one deleted with node-core/light) for the no-provider default.
Today
@sentry/node(and everything built on it) always installs an OpenTelemetry tracer provider + context strategy viainitOpenTelemetry. For v11 we want to flip the default: most SDKs should run without a tracer provider (corestartSpanAPIs + an AsyncLocalStorage context strategy for scope isolation, i.e. the old node-core/light model), and only the SDKs that genuinely need OTel span pickup (Next.js, SvelteKit) should default to the full tracer-provider setup.Users on any SDK must still be able to opt into a tracer provider when they want OTel spans surfaced in Sentry. We need to decide whether to introduce a new flag or reuse/rename an existing one, and settle the default per SDK.
Considerations
skipOpenTelemetrySetup,openTelemetryBasicTracerProvider,openTelemetrySpanProcessors. Prefer reusing/reframing over adding a fourth overlapping flag if we can.@sentry/node(the one deleted with node-core/light) for the no-provider default.@sentry/effectasync-context fix and the "light mode achievable with the regular node SDK" goal stated in ref(node): Merge@sentry/node-coreback into@sentry/node#22418.Acceptance criteria