Vercel Tracing Goes GA, Defaults On
Vercel Tracing is now generally available on every plan, with new Next.js 16.5 projects receiving tracing by default. Developers can inspect spans in the dashboard or search errors, latency, and trace data directly from the CLI.
Default-on observability makes production debugging dramatically more accessible, especially for teams building complex AI-backed applications. The tradeoff is that teams should still manage sampling, retention, and span volume as traffic grows.
- –`vercel traces search` brings trace investigation into terminal and CI workflows.
- –Filters for status, duration, services, deployments, and trace IDs make error triage much faster.
- –JSON output enables coding agents and automation to analyze traces programmatically.
- –Built-in tracing reduces the instrumentation work required for standard Next.js deployments.
- –Teams should review usage limits and sampling rules before treating full tracing as free at scale.
DISCOVERED
1h ago
2026-11-06
PUBLISHED
2h ago
2026-11-06
RELEVANCE
AUTHOR
vercel_dev