Vercel Tracing is now generally available on all plans. You can now search and inspect traces from the dashboard or the Vercel CLI, and new Next.js projects get tracing by default. Pricing is unchanged from the beta.
Copy link to headingBrowse and search traces in the dashboard
In beta, you could only open a trace per request from the Logs page. The new Traces page shows every trace and span in one place, for a project or your whole team. Switch between a Spans list and a Traces list, filter each, and search with Kibana Query Language (KQL). A Live mode streams new traces as they arrive. A query like span.name:db* AND span.duration > 500 narrows to slow database spans by name and duration.
Copy link to headingSearch traces from the CLI
The Traces page uses the same KQL as vercel traces search --query, so a query built in the dashboard runs in the CLI unchanged. Search covers every project in your team, or one project with the --project flag. Inspect a single trace with vercel traces inspect <request-id>, and manage a project's sampling rules with vercel traces config.
vercel traces search --query 'span.duration > 2000'vercel traces search --status error --since 1hFind spans slower than two seconds, then every error from the last hour.
Copy link to headingAutomatic tracing for new Next.js projects
In beta, nothing was collected until you added a sampling rule. Starting with Next.js 16.5, new projects created on Vercel that include at least one Node.js function get tracing turned on after their first successful build. Vercel adds one sampling rule tracing 100% of requests in all environments and injects instrumentation at build time, so traces include Next.js framework spans with no setup. To opt out, remove all sampling rules in Settings → Tracing.
Copy link to headingLonger retention
In beta, traces followed your runtime log retention. Hobby now keeps traces for 3 days instead of 1 hour, Pro for 14 days instead of 1 day, and Enterprise for 14 days instead of 3 days.
Read the Tracing documentation to learn more.