vercel traces

The vercel traces command helps you inspect request traces for a linked project or a specific project.

Use vercel traces get <request-id> to inspect a request trace.

# Get a specific trace
vercel traces get req_1234567890
 
# `get` is the default subcommand
vercel traces req_1234567890
 
# Open a trace in the Vercel Dashboard
vercel traces get req_1234567890 --open

The get subcommand returns details for a single trace by request ID.

vercel traces get req_1234567890
vercel traces get req_1234567890 --json

These options apply to vercel traces get.

The --project option, shorthand -p, specifies the project name or ID.

vercel traces get req_1234567890 --project my-app

The --json option, shorthand -j, returns machine-readable output.

vercel traces get req_1234567890 --json

The --open option opens the trace in the Vercel Dashboard instead of printing the trace in the terminal.

vercel traces get req_1234567890 --open

--open cannot be combined with --json.

Use --view with --open to set the initial Dashboard view. Supported values are timeline, tree, and waterfall.

vercel traces get req_1234567890 --open --view=tree
vercel traces get req_1234567890 --open --view=waterfall

--view requires --open.

Fetch a trace from a specific team and project:

vercel traces get req_1234567890 --scope my-team --project my-app

Open a trace in the dashboard tree view:

vercel traces get req_1234567890 --open --view=tree

Get JSON output for automation:

vercel traces get req_1234567890 --json

The following global options can be passed when using the vercel traces command:

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --non-interactive
• --scope
• --team
• --token
• --version

For more information on global options and their usage, refer to the options section.