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
{{ message }}
Repository navigation
Remove @opentelemetry/instrumentation dependency from @sentry/node #22759
After removing the iitm-based instrumentations (#22346) and the deprecated InstrumentationBase-derived classes, @sentry/node no longer registers any OpenTelemetry/import-in-the-middle module patchers. But it still depends on @opentelemetry/instrumentation for a handful of live imports. This ticket tracks vendoring/reimplementing those so we can drop the dependency, mirroring the @opentelemetry/core removal effort in #21674.
packages/node/src/otel/instrument.ts — registerInstrumentations, Instrumentation (type). Backs generateInstrumentOnce, which is a public export (src/index.ts).
packages/node/src/utils/ensureIsWrapped.ts — isWrapped. Used by the Express/Koa/Hapi/Fastify error-handler setup to warn if the app object wasn't wrapped.
Type-only imports (trivial to inline):
packages/node/src/integrations/http/SentryHttpInstrumentation.ts — InstrumentationConfig, base of the public SentryHttpInstrumentationOptions.
packages/node/src/integrations/tracing/redis/vendored/types.ts — InstrumentationConfig, base of the redis cache option types used by cache.ts.
Work
Reimplement or vendor registerInstrumentations + the Instrumentation type behind generateInstrumentOnce (or evaluate whether generateInstrumentOnce still needs to exist at all now that nothing internal calls it — it only remains as a public export).
Activity
linear-code commentedon Jul 28, 2026
JS-3203