Caddi
Sign inSign up

caddi logs

Stream Vercel runtime logs for the current environment, with the noise filtered out by default.

Usage

bash
caddi logs [flags]

Common invocations

bash
# Tail dev (default — uses the env linked to your current branch)
caddi logs --tail

# Production, last 1 hour
caddi logs --env production --since 1h

# Only errors
caddi logs --env production --level error --tail

Flags

  • --tail — keep streaming. Otherwise prints the last 200 entries and exits.
  • --since <duration> — 5m, 1h, 2d.
  • --level <info|warn|error> — minimum log level.
  • --source <function|edge|build> — narrow to one runtime.
  • --grep <pattern> — regex filter applied client-side.

Output

bash
12:14:22  INFO    /api/contact     submit ok           id=sub_01H9X4...
12:14:31  ERROR   /api/checkout    stripe 4xx          status=402 customer=cus_NA...
12:14:31  INFO    /api/contact     submit ok           id=sub_01H9X5...
12:14:48  WARN    middleware       slow auth lookup    duration=812ms

Logs come from Vercel’s log drain. If you’ve also wired Sentry or Better Stack, those remain the source of truth — caddi logs is for fast iteration, not long-term storage.

Next

caddi listen →