Node.js Tracing Channels offer a native alternative to monkey-patching for APM instrumentation. Traditional approaches — monkey-patching in CommonJS and Module Customization Hooks in ESM — apply observability 'from the outside', which is brittle and breaks with ES Modules. Tracing Channels, part of the Node.js Diagnostics Working Group's work, let libraries proactively emit structured telemetry for their own lifecycle events (start, end, error, asyncStart) with near-zero overhead when unused. APM tools like Sentry and OpenTelemetry can subscribe to these channels without coupling to specific libraries. The ecosystem is already adopting this: undici, fastify, nitro, h3, mysql2, unstorage, ioredis, and node-redis have shipped or merged support. The naming convention uses npm package names as namespaces to avoid collisions. The goal is universal JS observability across Node.js, Bun, and Deno without fragile workarounds.
