Send Railway logs to LogPulse
Railway deployment events, build logs, runtime logs and platform alerts.
Configure → Sources → Cloud. LogPulse reads the Railway GraphQL API and webhooks itself, without an agent. Events land in the cicd, application indexes with source railway and fill the CI/CD Pipeline data model.Overview
- Railway GraphQL API and webhooks to Integration poller
- Integration poller to index=cicd
- Integration poller to index=application
LogPulse signs in to Railway with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- Railway API token (Account, Workspace, or Project token)
- Project ID (Cmd+K in Railway dashboard)
- Optional: Environment ID and Service ID for filtering
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Railway
| Field in LogPulse | Where you find it |
|---|---|
| API Token | In Railway: Account Settings, Tokens. An Account, Workspace or Project token works; build and runtime logs need an Account or Team token. Stored encrypted and never shown again. |
| Project ID | Press Cmd+K in the Railway dashboard and choose Copy Project ID. |
| Environment ID (optional) | Leave empty to monitor all environments. |
| Service ID (optional) | Leave empty to monitor all services. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Railway. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
Deployment Events is not polled but sent to LogPulse by Railway. After you save, LogPulse shows the address and the key to set on the Railway side.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Deployments | cicd | railway | cicd_pipeline | Deployment lifecycle events: build status, deploy status, rollbacks, and crashes. |
| Build Logs (off by default) | cicd | railway | railway:build:log | Raw build output logs for each deployment (Nixpacks/Dockerfile build steps). Requires an Account or Team API token. |
| Runtime Logs (off by default) | application | railway | railway:deploy:log | Application stdout/stderr logs from running deployments. Requires an Account or Team API token. |
| Deployment Events | cicd | railway | railway:webhook | Real-time deployment status changes and resource alerts via Railway webhooks. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Railway without changes.
Fields and data models
| Data model | What you get |
|---|---|
| CI/CD Pipeline | Deployment events with status, trigger, repository, branch, actor, duration, environment and service name. |
Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (cicd, application) source IN (railway)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| API token is invalid or expired. | Generate a new token at Railway, Account Settings, Tokens, or create a Project Token in the project settings. |
| Token does not have access to this project. | A Project Token only works for its own project. Check the project ID (Cmd+K, Copy Project ID). |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Railway may also simply have had nothing new. |
Frequently asked questions
- How do I send Railway logs to LogPulse?
- Add the Railway cloud integration under Configure, Sources, Cloud in LogPulse and fill in API Token, Project ID. LogPulse reads the Railway GraphQL API and webhooks itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Railway?
- Railway API token (Account, Workspace, or Project token). Project ID (Cmd+K in Railway dashboard). Optional: Environment ID and Service ID for filtering. Read access is enough for collecting logs.
- Which index does Railway data go to?
- The index is the kind of data: cicd, application. The source is the product: railway. Each data source has its own sourcetype, listed on this page.
- Which data models does Railway fill?
- CI/CD Pipeline. Detection rules and dashboards written for a data model work on Railway without changes.
- Why is Build Logs and Runtime Logs off by default?
- To keep your daily ingest down until you need it: Build Logs, Runtime Logs are high volume or of use to fewer teams. Tick the data source in the integration to switch it on.