Vercel Tracing is now generally available
Vercel Tracing reached general availability on all plans. The new Traces page in the dashboard and the vercel traces CLI commands allow searching and inspecting traces with KQL, and new Next.js projects get tracing enabled by default after their first successful build.
Why it matters
Builders on Vercel can search and inspect request traces across a project or team instead of opening traces one request at a time from the Logs page. Trace retention is longer on every plan, and pricing is unchanged from the beta. New Next.js projects with a Node.js function get framework spans without setup, but the default sampling rule traces 100% of requests in all environments.
Who should care
Developers and teams running Next.js or other Node.js functions on Vercel, especially those debugging slow database calls or latency issues.
What you can do
Open the Traces page in the Vercel dashboard or run vercel traces search, and review the Settings → Tracing sampling rules for existing or new projects to confirm they match your data and cost expectations.