Newest guideDebugging
How to find the cause of a 5xx fast
A five-step routine for a burst of 500 errors: find when it started, filter to status:5xx, follow one request id, read the lines around it, then fix.
Sam 5 min read
Read the guide
Logyak guides 4 guides
Guides to logs that answer questions
Practical guides on getting logs out of each platform, structured logging, and finding the cause of an error fast.
Search
Structured logging in Node.js you can search
Plain text logs are easy to write and hard to search. One JSON object per line, with the right four fields, fixes that. Examples with console.log and pino.
5 min read
Platforms
Vercel log drains explained
A Vercel drain posts your function, edge, build and request logs to a URL. What arrives, how to verify it, and how to set one up for searchable history.
5 min read
Platforms
How to get logs out of Railway
Railway does not push logs anywhere. Here is what the CLI and the API can do, and how to keep searchable history without writing a poller yourself.
5 min read
Browse by topic
Platforms Getting logs out of Railway, Vercel, Netlify and Render into one place.2 guidesSearch Finding the right lines fast with levels, services, status codes and phrases.2 guidesDebugging Reading errors, tracing a request and working out what went wrong.1 guideNode.js Structured logging from Node apps and sending it over HTTP.1 guideRailway App and HTTP request logs from Railway, pulled with an API token.1 guideVercel Vercel log drains: function, edge and request logs.1 guide
Search every app's logs in one place
Connect Railway, Vercel, Netlify or Render in two minutes, and find the line that matters.
Start free