railway trace adds tracing settings and traces

Introduced 2026-09-23 · score 0.91

HOW TO USE IT

When debugging a Railway project, use `railway trace status` to inspect tracing settings and `railway trace list` / `railway trace get <TRACE_ID>` to inspect traces. [Railway CLI trace docs](https://docs.railway.com/cli/trace)

WHY THIS HELPS

Inspect tracing settings and traces while debugging a Railway project.

REQUIREMENTS AND LIMITATIONS

• Version: v5.60.0
• railway trace status (required): Subcommand to show tracing settings and the last exported span times.
• railway trace list (required): Subcommand to list traces, newest first.
• --since <TIME>: Start of the time window; relative time or ISO 8601. Defaults to `1h`.
• --errors: Only include traces with an error span; adds `@status:error` to the filter.
• railway trace get <TRACE_ID> (required): Subcommand to show one trace; `<TRACE_ID>` is a required W3C trace ID of 32 hexadecimal characters.
• -s, --service <SERVICE>: Service name or ID; defaults to the linked service.
• -e, --environment <ENV>: Environment to use; defaults to the linked environment.
• -p, --project <PROJECT_ID>: Project to use; defaults to the linked project. When set, also pass `--environment`.
• --json: Output in JSON format.
• --service and --all: Mutually exclusive for applicable subcommands; `--all` selects every service in the environment.
• Prerequisite: Tracing is a preview feature under active development.
• Prerequisite: Commands use the linked service, environment, and project by default; pass `--service`, `--environment`, or `--project` to select them explicitly.
• Prerequisite: A project token in `RAILWAY_TOKEN` can run `status`, `list`, and `get`; changing tracing requires a user or workspace token.

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.60.0
• https://docs.railway.com/cli/trace

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

Report a problem with this card