Search trace spans from the Vercel CLI

Vercel released a `vercel traces search` command in its CLI that lets developers and coding agents search a project's trace spans from the terminal, returning up to 100 spans from the last hour, newest first, by default. The command filters results by environment, service, span name, status, deployment ID, request ID, trace ID, or span ID, supports `--since` and `--until` time ranges, accepts Kibana Query Language (KQL) via `--query` for fields such as duration, and outputs one JSON object per span with `--json` for scripts and agents. Users update via `vercel upgrade` and can view options with `vercel traces search --help`.

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, vercel traces search 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 --since and --until : For filters without a dedicated option, use --query with Vercel's supported subset of Kibana Query Langugage KQL https://www.elastic.co/docs/reference/query-languages/kql . It supports fields such as duration, along with span and resource attributes: Add --json to output one JSON object per span, giving scripts and agents structured data to analyze. Update to the latest Vercel CLI with vercel upgrade , then run vercel traces search --help to see all available options. Learn more in the vercel traces documentation https://vercel.com/docs/cli/traces .