Repository navigation
Conversation
logaretm
force-pushed
the
diagnostics-channel-tracingchannel-stable
branch
from
July 15, 2026 19:40
fa3476f to
5b8df3d
Compare
logaretm
marked this pull request as ready for review
July 15, 2026 19:43
bjohansebas
approved these changes
Jul 15, 2026
Member
|
cc: @nodejs/diagnostics |
Promotes the diagnostics_channel.tracingChannel() factory and the TracingChannel class from experimental to stable. TracingChannel has been available since v18.19.0 / v19.9.0 with an unchanged surface and now has broad adoption: fastify, pino, mysql2, redis, ioredis, mongoose, graphql, h3, srvx, and the Vercel AI SDK publish TracingChannel events natively, and it is consumed by OpenTelemetry, Sentry, Datadog, and New Relic. The last behavioral wart, tracePromise stripping custom thenables (nodejs#59936), was resolved in nodejs#61766. This mirrors the scoping in nodejs#45290: BoundedChannel, the bindStore / runStores store helpers, and the concrete built-in channels stay experimental. Signed-off-by: Abdelrahman Awad <abdelrahman.awad@sentry.io>
logaretm
force-pushed
the
diagnostics-channel-tracingchannel-stable
branch
from
July 15, 2026 20:15
5b8df3d to
e445b63
Compare
timfish
approved these changes
Jul 15, 2026
jasnell
approved these changes
Jul 19, 2026
timfish
approved these changes
Jul 20, 2026
AbhiPrasad
approved these changes
Jul 20, 2026
Member
|
cc: @Qard |
Member
|
From what I understand from the Node.js Collaborator Guide, it needs to be released in a major version. |
This PR Promotes the
TracingChannelAPI (thediagnostics_channel.tracingChannel()factory and theTracingChannelclass) from experimental to stable.TracingChannel has been available since v18.19.0 / v19.9.0 with an unchanged surface, and now has broad real-world adoption: fastify, pino, mysql2, redis, ioredis, mongoose, graphql, h3, srvx, and the Vercel AI SDK publish TracingChannel events natively, and it's consumed by OpenTelemetry, Sentry, Datadog, and New Relic.
IMO, The last behavioral wrinkle in the base API was
tracePromisestripping custom thenables (#59936), which was resolved semver-major in #61766 and landed in v26.0I marked this as stable given the adoption and signals given that the API is stable and backward compatible.
I'm also suggesting we back port this to v26 docs