Railway

How it works

Railway has no log drains. Logyak reads your logs through Railway's public API instead: every 30 seconds it asks for the app logs of the environment you picked (every service in it, in one call) and, if you want them, the HTTP request logs of each live deployment. Nothing is installed in your project and nothing is redeployed.

Steps

1. In Railway, open Account Settings → Tokens and create a token. A workspace token sees every project of that workspace; a project token sees one environment only.
2. In Logyak, open Sources → Add a source → Railway, paste the token and click Find projects.
3. Pick the project and environment, choose whether to collect HTTP request logs, and create the source.
4. Click Check now on the source page. The first read goes back 10 minutes, so recent lines show up at once.

Good to know

• The token is stored encrypted and never shown again. If Railway refuses it later, the source pauses and says so; paste a new token on the source page.
• Each line carries the Railway service name, so service:api narrows a search to one service.
• HTTP logs carry method, path, status and duration: try kind:http status:5xx.
• Railway sends whatever an app writes to stderr as an error; Logyak re-reads the words, so a normal message on stderr is stored as info.