Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt

Use this file to discover all available pages before exploring further.

The Railway integration monitors your services for deployment failures and crashes, and streams live logs directly to LogBrew. When a service crashes or a deployment fails, you get a push notification before you’ve had a chance to open your laptop.

​
What you’ll see

  • Deployment failed: a deployment encountered an error and did not complete
  • Deployment crashed: a running deployment crashed unexpectedly (Critical)
  • Deployment started: a new deployment has begun
  • Build logs: live output from the build process
  • Deployment logs: live runtime output from your running service

​
Connect Railway

1

Open Add Project

In the LogBrew app, tap the Projects tab, then tap Add Project.
2

Select Railway

Tap Railway from the list of available integrations.
3

Authorize with OAuth

LogBrew opens the Railway authorization screen. Approve the requested permissions for your Railway account.
4

Select a service

After authorization, choose which Railway service you want to monitor. LogBrew creates one project per connection, scoped to the service you select.
5

Done

LogBrew begins delivering deployment events and streaming live logs for your service. The project appears in your feed immediately.
One Railway connection equals one LogBrew project. The integration is scoped to the service you selected during setup. To monitor additional services, add them as separate projects from the Projects tab.

​
Severity mapping

Railway includes severity information in its event payloads. LogBrew uses those values directly:
Railway severityLogBrew severity
CRITICALCritical
WARNINGWarning
INFOInfo

​
Log streaming

LogBrew streams build and deployment logs in real time using Railway’s GraphQL subscription API. Logs appear in the Logs tab for your project as soon as Railway produces them. No refresh needed. Log streaming is active while your deployment is building or running. When a deployment reaches a terminal state (failed, crashed, removed), streaming stops automatically.