Search trace spans from the Vercel CLI
The Vercel CLI now supports searching trace spans directly from the terminal via the vercel traces search command, allowing developers to investigate errors, latency, and security issues without accessing the dashboard. The command returns up to 100 spans from the last hour by default and supports filtering by environment, service, span name, status, deployment ID, request ID, trace ID, span ID, and time range.
You and your coding agents can now search a project’s trace spans from the terminal with . vercel traces search
Each span represents one step in a request, helping you investigate errors, latency, and security-related behavior without opening the dashboard.
By default, returns up to 100 spans from the last hour, newest first, so you can search without first finding a request or trace ID. Filter results by environment, service, span name, status, deployment ID, request ID, trace ID, or span ID, or narrow the time range with and :vercel traces search--since--until
For filters without a dedicated option, use with Vercel's supported subset of . It supports fields such as duration, along with span and resource attributes:--queryKibana Query Langugage (KQL)
Add to output one JSON object per span, giving scripts and agents structured data to analyze.--json
Update to the latest Vercel CLI with , then run to see all available options. Learn more in the .vercel upgradevercel traces search --helpvercel tracesdocumentation
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Muse Wonder now available on AI Gateway
Meta's Muse Wonder model is now accessible through Vercel's AI Gateway, supporting coding tasks, multi-step agent workflows, and computer use with a 1M-token context window. Users can access the model via a single API key without creating a separate Meta account and use it for text, image, PDF processing, tool calling, and structured outputs.
Agents can now buy domains with the Vercel CLI
Vercel CLI now enables agents to discover, check availability, and initiate domain purchases through structured commands, with purchase confirmation remaining under user control via interactive terminal or dashboard approval.
New Pro teams default to 30-day deployment retention
Pro teams now default to a 30-day deployment retention period to balance keeping recent history available while reducing storage costs. You can configure a longer retention period in team settings if needed.