Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

vercelAIIntegration: record AI SDK v7 runtimeContext (filtered by telemetry.includeRuntimeContext) as span attributes

未關閉
  • 哪裡不對？
#24,706 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
observability

研究方向

Start at the v7 channel subscriber, especially buildInvokeAgentSpan and the existing callId maps in @sentry/server-utils. Check how runtimeContext is published and how the related vercel/ai filtering fix affects supported versions before tracing child generate_content and execute_tool spans. Done means opted-in requestId and tenantId reach the intended spans, apiToken does not, and coverage verifies the version behavior.

由索引模型根據 Issue 內容生成。

描述

Bug Spans
Problem Statement

AI SDK v7 removed telemetry.metadata. Per-call metadata now goes in runtimeContext, and the app opts keys into telemetry with telemetry.includeRuntimeContext (telemetry docs, runtime context docs). @ai-sdk/otel records the included keys as ai.settings.runtimeContext.*. On v6 the equivalent data arrived through experimental_telemetry.metadata as vercel.ai.telemetry.metadata.*.

The v7 channel subscriber in @sentry/server-utils (vercel-ai-dc-subscriber, added in #21613) never reads runtimeContext, so on v7 there is no way to attach request-level metadata (user, tenant, request id, ...) to gen_ai spans. The integration docs say not to combine registerTelemetry with vercelAIIntegration, so registering @ai-sdk/otel alongside it is not a workaround either.

await streamText({
  model,
  messages,
  runtimeContext: { requestId: 'req_123', tenantId: 'acme', apiToken: 'secret' },
  telemetry: {
    isEnabled: true,
    functionId: 'support-chat',
    includeRuntimeContext: { requestId: true, tenantId: true },
  },
});
  • Expected: the gen_ai.invoke_agent span (and ideally its gen_ai.generate_content / gen_ai.execute_tool children) carries requestId and tenantId, and not apiToken.
  • Actual: none of the keys appear. The span has only vercel.ai.operationId, vercel.ai.model.provider, vercel.ai.settings.maxRetries and the gen_ai.* attributes.

Checked against @sentry/node 10.71.0 and the @sentry/server-utils subscriber in 10.75.3 and 11.0.0, with ai 7.0.100 / 7.0.113 on Node.

Solution Brainstorm
  • In buildInvokeAgentSpan, set one attribute per event.runtimeContext key. vercel.ai.settings.runtimeContext.<key> would match @ai-sdk/otel's ai.settings.runtimeContext.* under the existing ai.* to vercel.ai.* renaming.
  • Copy the same attributes onto child generate_content / execute_tool spans through the existing callId maps (like operationIdByCallId), since those channel events do not carry runtimeContext.
  • Optionally, record event.toolContext on execute_tool spans, which the AI SDK filters by telemetry.includeToolsContext.

Dependency on the AI SDK. In ai <= 7.0.113 the channel publishes runtimeContext / toolsContext unfiltered, ignoring includeRuntimeContext (vercel/ai#21442). Reading event.runtimeContext on those versions would send keys the app never opted in to telemetry. The fix is open in vercel/ai#21447, which filters channel events the same way as registered integrations. So this should only read the field on AI SDK versions that include that fix, or otherwise guard against unfiltered context.

Additional Context

#24660 notes the same gap from the Cloudflare Think side ("neither subscriber reads either field").

主要語言
TypeScript
星號
8.7k
分支
1.9k
平均合併
1 天 15 小時
30 天內合併 PR
495

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

getsentry/sentry-javascript 的其他 Issue

查看 getsentry/sentry-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。