docs(nextjs): Require experimental_telemetry for Vercel AI - #19197
Merged
Conversation
On Next.js the SDK cannot auto-enable the Vercel AI SDK's telemetry, so `experimental_telemetry` is required on every call in both the Node and Edge runtimes. The page scoped that requirement to Edge and claimed the Node runtime patches call sites automatically. Also correct the troubleshooting entry for raw span names. It presented `force: true` as the complete fix, but `force: true` alone only registers the span processors — following it as written produced no AI spans at all. Simplify the Next.js runtime split while here: it is kept for setup, where the two runtimes need different config files, and dropped where both runtimes now behave the same. Refs getsentry/sentry-javascript#23773 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
removed
the
Priority: Normal
github-actions
Bot
added
the
Priority: Needs Triage
chargome
marked this pull request as ready for review
September 1, 2026 05:15
Contributor
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
obostjancic
approved these changes
Sep 1, 2026
JPeer264
approved these changes
Sep 1, 2026
Raw `ai.*` span names mean the AI SDK is already emitting telemetry, so `experimental_telemetry` is not the missing step for that symptom — the span processors are. Lead with `force: true` and keep `experimental_telemetry` as something to preserve and extend, not to discover. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
3 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.
DESCRIBE YOUR PR
On Next.js,
experimental_telemetry: { isEnabled: true }is required on every AI SDK call in both the Node and Edge runtimes — the page scoped this to Edge and claimed the Node runtime patches call sites for you.The troubleshooting entry for raw span names presented
force: trueas the whole fix, but alone it only registers the span processors and yields zero AI spans; it now spells out both required steps. Verified on@sentry/nextjs@10.71.0, Next.js 16.3.3,ai@6.Also trimmed the Node/Edge split down to where the runtimes actually differ. Not version-gated, since the fix that makes
force: trueunnecessary (getsentry/sentry-javascript#23773) is unreleased. The page is shared across ~25 platforms — every edit is inside ajavascript.nextjs<PlatformSection>.