sincecutoff.com
← all changes

railway logs adds HTTP request logs

Introduced 2026-03-18 · score 0.99

HOW TO USE IT

When debugging a Railway service, use `railway logs --http` to stream edge request logs live in a terminal; add `--lines` for historical logs, `--filter` for query filters, or `--json` for newline-delimited JSON.

railway logs --http --lines 50
railway logs --http --filter "@path:/api/users @httpStatus:200"
railway logs --http --json --filter "@requestId:<request-id>"

WHY THIS HELPS

Inspect or stream HTTP request logs while debugging a Railway service.

BEFORE THIS CHANGE

Use the existing CLI workflow for build and deploy logs, which did not include HTTP request logs.

REQUIREMENTS AND LIMITATIONS

  • Version: v4.32.0
  • --http (required): Select HTTP request logs; log type flags are mutually exclusive.
  • --lines <N>: Fetch N log lines; disables streaming.
  • --filter <QUERY>: Filter with Railway query syntax, including `@path`, `@httpStatus`, and `@requestId`; supports AND, OR, negation, and numeric comparisons/ranges.
  • --json: Output logs in JSON format; HTTP output is newline-delimited JSON.
  • Live follow for HTTP logs is available from an interactive terminal.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card