diagnostics_channel: mark TracingChannel as stable#64525
Open
logaretm wants to merge 1 commit into
Open
Conversation
nodejs-github-bot
added
diagnostics_channel
logaretm
force-pushed
the
diagnostics-channel-tracingchannel-stable
branch
from
fa3476f to
5b8df3d
Compare
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
5b8df3d to
e445b63
Compare
timfish
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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