Skip to main content
All Railway integration capabilities

About

Send your Railway deploy logs, HTTP logs, and traces to Sazabi. Railway has no platform log drain, so you run the sender in your own project, in one of two ways:
  • Deploy the forwarder (no code changes). The Sazabi forwarder is a Railway service you add from a template. It reads the deploy and HTTP logs of every service in its environment from Railway’s API and sends them to Sazabi. Services you add later are picked up automatically. Logs only.
  • Instrument your app with OpenTelemetry. Your application sends logs and traces through its OpenTelemetry SDK. Use this path for traces.

Prerequisites

Set up in the dashboard

Option A: Deploy the forwarder (no code changes)

Deploy on Railway
Railway’s log API accepts only account tokens, and an account token can read every project in your Railway account, including projects the forwarder does not run in. Project and workspace tokens do not work. Revoke the token if you remove the forwarder.
1

Create a Railway account token

Open railway.com/account/tokens and create a token with Workspace left unset.
2

Deploy the template

Click Deploy on Railway and choose the project and environment whose logs you want. Set the two variables:The template sets RAILWAY_ENVIRONMENT_ID itself. Deploy one forwarder per environment you want to send.
3

Send traffic

Send some traffic to a service with a public domain, or trigger a deploy. The forwarder sends:
  • Deploy logs from every service, with Railway’s log level as the severity.
  • HTTP logs for every service with a public domain: ERROR for 5xx, WARN for 4xx, INFO otherwise.
Every log carries service.name, deployment.environment.name, railway.project.name, and the Railway project, environment, service, and deployment IDs. Logs written before the forwarder started are not backfilled.
The forwarder sends logs only, because Railway’s API has no traces. To send traces, also follow Option B for those services. Source and configuration: github.com/sazabi/railway-forwarder.

Option B: Instrument your app with OpenTelemetry

1

Set Railway variables

Add these variables in the Railway service Variables page. OTEL_EXPORTER_OTLP_ENDPOINT is your intake URL (shown above). Railway fills in the ${{...}} references from its own service and deployment metadata.
OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED is what sends Python logging lines; without it only traces arrive. Node services can leave it set.Railway previews the staged variable change set — review and deploy it when prompted.
2

Bootstrap the runtime

Install the OpenTelemetry packages for your runtime and load auto-instrumentation at startup.Log through your runtime’s logger: Python logging, or pino, winston, or bunyan on Node. print and console.log stay in Railway’s deployment logs; the SDK does not forward stdout.Node.js
Python
3

Redeploy and verify

Review and deploy the staged variable change set when prompted, then send some traffic to the service.
4

Hand off the change

Commit these changes on a new branch, push it, and open a pull request. Keep the intake URL and any keys in environment variables or a secret store, and commit only configuration that references them.

Set up with the CLI

You can also register the Railway log source with the Sazabi CLI (installed and authenticated — see CLI reference). Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.

Verify

Send traffic to your Railway service, or trigger a deploy. Open the Intake page in the Sazabi dashboard and confirm logs or traces from the Railway source appear. Records typically arrive within a minute or two of the request. If nothing appears on the forwarder path, open the forwarder service’s logs in Railway. On the SDK path, check the Railway deployment logs for OpenTelemetry exporter errors and confirm your app is sending through OpenTelemetry, not only to stdout.

Troubleshooting

Forwarder logs Not Authorized — RAILWAY_API_TOKEN is not an account token, or it was revoked. Create a token with Workspace left unset. Forwarder logs intake rejected batch — SAZABI_INTAKE_URL is wrong. Copy the intake URL from the Railway log source again. No HTTP logs for a service — Railway records HTTP logs only for services with a Railway or custom domain. No telemetry appears — Confirm OTEL_EXPORTER_OTLP_ENDPOINT is set on the service variable, not only at build time. Check the Railway deployment logs for OTLP exporter errors. Metrics are not stored — Sazabi does not store OpenTelemetry metrics sent to this endpoint. Point your metrics exporter at the OpenTelemetry Metrics source instead.

Further reading

Intake

See per-source ingestion volume and health in the Intake page.

Instrument

Learn how to send data to Sazabi.

Log sources

Browse the full log source catalog.