Last 12 weeks · 2 commits
1 of 6 standards met
My understanding is that all of this code runs only server-side In that case, there is no benefit to trying to fallback to (the only case where it's necessary is for client-side code, where there is obviously no at runtime.) This means that the JS chunks in the serverless function are now deterministic as always inlined the value into the JS chunk
Repository: vercel/otel. Description: OTEL tracing for Vercel Stars: 90, Forks: 21. Primary language: TypeScript. Languages: TypeScript (96.4%), JavaScript (3.1%), CSS (0.4%), HTML (0.1%). Homepage: https://vercel.com/docs/observability/otel-overview Latest release: @vercel/otel@2.1.1 (1w ago). Open PRs: 9, open issues: 37. Last activity: 1w ago. Community health: 37%. Top contributors: jankaifer, dvoytenko, github-actions[bot], kakadiadarpan, gaspar09, agadzik, MaxLeiter, bripkens, bengigone, ethshea and others.
TypeScript
Description When is enabled via in , external fetch calls return empty response bodies. This breaks: Clerk SDK (, etc.) MCP SDK OAuth token exchange Any external API fetch that reads response body Environment Next.js 15 (App Router) 1.10.0 Deployed on Vercel Reproduction 1. Enable OTel in : 2. Make a fetch call to an external API: Behavior Local: Works correctly, response body is populated Vercel: Response status is 200, but body is empty (0 bytes) Workaround Only enable OTel when explicitly configured: Related Possibly related to #135 (FormData Error) Possibly related to #161 (fetch not being traced) The fetch patching appears to interfere with response body consumption in certain scenarios.
I have initialized the dd-trace tracer and registered vercel otel instrumentation in my app router instrumentation hook. I can see nextjs APM traces coming through to datadog, but any cases where I use the datadog tracer to create custom spans etc do not seem to work. i.e. Built in, automatic spans, for "executing api route X" and outbound requests are traced. But my custom are not being traced.