Source: vercel.com/changelog/vercel-tracing-is-now-generally-available
The new Traces page lists every trace and span for a project or for a whole team, replacing the beta behavior of opening one trace per request from the Logs page. Users can switch between Spans and Traces lists, filter each, search with Kibana Query Language (KQL) and use a Live mode that streams new traces as they arrive.
The Vercel CLI gets matching search commands. The dashboard and the vercel traces search --query command use the same KQL, so a query built in one runs in the other. Search covers the whole team by default or a single project with the --project flag, and vercel traces inspect and vercel traces config handle individual traces and sampling rules.
New Next.js projects that include at least one Node.js function get tracing turned on after their first successful build, starting with Next.js 16.5. Vercel adds a sampling rule that traces 100% of requests in all environments, and users can opt out by removing all sampling rules in Settings → Tracing. Retention also rises: Hobby keeps traces for 3 days, Pro and Enterprise for 14 days.
Why it matters if you build agents
Agent developers on Vercel can find slow database spans or recent errors from the dashboard or a terminal without opening each request's logs. Teams that want the same queries in scripts can run them unchanged through the CLI.
Next.js projects created after this change will collect traces by default at a 100% sampling rate, so developers who want to limit trace volume or cost should review the sampling rules in Settings → Tracing.
Get stories like this every weekday
One short email with the day's agent tooling news.