Search trace spans from the Vercel CLI
Vercel CLI now lets you search trace spans from the terminal — no dashboard required, agent-friendly JSON output included.
Why it matters
Vercel adds observability tooling (CLI-based trace search with KQL filtering and JSON export) that makes debugging distributed requests faster for developers and agents. Useful for latency investigation and error diagnosis, but incremental product feature rather than a capability shift.
The key facts
10 to knowvercel traces search command returns up to 100 spans from last hour by default
Filters available: environment, service, span name, status, deployment ID, request ID, trace ID, span ID, time range (--since, --until)
--query flag supports Kibana Query Language (KQL) subset; supports duration and span/resource attributes
--json flag outputs one JSON object per span for agent/script consumption
Requires latest Vercel CLI version; documentation available in vercel traces
vercel traces search CLI command ships; defaults to 100 spans from last hour, newest first
Filters: environment, service, span name, status, deployment ID, request ID, trace ID, span ID, time range
--query flag supports Kibana Query Language (KQL) subset; fields include duration, span and resource attributes
--json output produces one JSON object per span for structured analysis by scripts and agents
Available via vercel upgrade to latest CLI
Go to the source
Vercel Blogvercel.com
Publisher excerpt: 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…