Log order not preserved
fluidsonic
PROOP

a month ago

Hey there 👋

We have quite some challenges in everyday monitoring and debugging, because Railway doesn't preserve the order of printed log lines. This is different from Heroku (and any other platform), which we are evaluating a migration from - towards Railway.

For example, when we pretty-print a JSON object using a single print/console.log in the code, the individual JSON lines are mixed up, and sometimes even mixed up with other log messages.

We have this issue with our Java deployments as well as with Node.js deployments.
We have this issue on [railway.com](railway.com) as well as with railway logs.

How can we ensure that logs are presented properly by Railway, just like everywhere else?

3 Replies

This is a platform issue, I believe they are working on correcting it.


(It's an issue I've seen happen in the Docker runtime for as long as I've used it, I suspect it's the underlying cause)


brody
EMPLOYEE

a month ago

Hello,

We are aware of this issue, it should be fixed on our next runtime release, but until then, you would want to print minified JSON.


Loading...