railway trace adds per-environment tracing in IaC
Introduced 2026-09-28 · score 0.95
HOW TO USE IT
When configuring tracing for a Railway environment, set the service’s `tracing` switches in IaC or enable tracing for that environment with `railway trace`.
const api = service("api", { tracing: { enabled: true, autoInstrumentation: true } });railway trace enable --service <SERVICE> --environment <ENVIRONMENT>WHY THIS HELPS
Configure tracing separately for each environment in an IaC setup or through `railway trace`.
REQUIREMENTS AND LIMITATIONS
- Version: v5.63.0
- tracing.enabled: Enables edge tracing and adds `OTEL_*` variables on the service’s next deploy. Omitted or `false` means tracing is off.
- tracing.autoInstrumentation: Enables automatic instrumentation; it only takes effect while `enabled` is true. The docs do not say the two switches are mutually exclusive.
- --service <SERVICE>: Service name or ID; defaults to the linked service. Conflicts with `--all`.
- --environment <ENV>: Selects the environment; defaults to the linked environment.
- Prerequisite: IaC tracing requires CLI 5.63.0 or newer and a compatible SDK: TypeScript `railway` 3.12.0+, Python `railway-sdk` 0.4.0+, or Go `railway-go-sdk` v0.3.0+.
- Prerequisite: Changing tracing with `railway trace enable` requires a user or workspace token; a project token in `RAILWAY_TOKEN` cannot enable tracing.
- Prerequisite: Tracing is a preview feature under active development.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v5.63.0
- https://docs.railway.com/infrastructure-as-code/reference
- https://docs.railway.com/cli/trace
Check the installed version and the source before using it. Entry JSON