Vercel Tracing

Use Vercel Tracing to instrument server code with OpenTelemetry and inspect spans from deployed traffic. The workflow is register @vercel/otel from the framework's server startup hook → deploy and exercise a server route → search and inspect the trace with vercel traces. Use the same traces to debug failed requests and measure slow operations. Read only the references needed for the current task.

Tracing only covers requests that run server code: dynamic routes, API routes, functions, and on-demand rendering. Static and prerendered pages and CDN cache hits run no application code, so traces cannot explain or speed them up; optimize those with caching, bundle size, and Core Web Vitals work instead.

Reference index