2 years ago
No deployment logs. All output sent to stdout will be displayed here
my logs are not coming from a spring boot app. any suggestions?
35 Replies
2 years ago
Does this persist even after redeploying?
2 years ago
there is a ratelimit in logs, perhaps you're exceeding the rate limit
2 years ago
I'm not sure what the rate limit exactly is 🤔
2 years ago
Nevermind, I swear I remember one of the conductors mention a log rate limit, but I can't seem to find anything like that
yes i have the same problem, if i hit the limit, it would be nice if i would get nottified about it
2 years ago
I have brought this up to the team, there is definitely a limit and the limit should be listed in the technical specifications section of the docs, but it's not right now.
however, you would still see some logs, it's just that the logs that go over the threshold are discarded, it's also a very reasonable limit, so I'm confident in saying that you are not running into any logging limits.
what I do think is happening is that some of the logging infrastructure was shut down yesterday during the incident and unfortunately yours never got reconnected.
2 years ago
Thank goodness, thought I was schizo or something
2 years ago
<@1060856209332260864> - missing all deployment logs
2 years ago
Looking
2 years ago
<@778644535948869724> can you link to your service please?
That's not a valid project ID
2 years ago
open your service and then copy the url, paste it here
2 years ago
ray works for railway and is the only one who would be able to look at the project
2 years ago
all good
2 years ago
This is the testing env right? You have a deployment from 2hrs ago and the logs appear to be fine
2 years ago
Is it just a single inactive deployment missing logs?
2 years ago
there's nothing in the docs yet, and tbh I've found that most people would never hit the log per second limit unless they where absolutely spamming console.log, exactly what the limit is there to prevent, from my experience, it's a very sensible limit.
but limits should of course always be documented, so I will bump this to the right person!
So I reckon streaming to a .log file is the way to go if I were to stress test?
Or is also writing to a stream restricted? Dk how this limits work or apply, didnt test yet
2 years ago
you could stream as fast as you want to a file, but that wouldn't cause logs to show on the deployment logs.
the limit is simply just how many log lines per second railways logging infrastructure will process before it drops log lines, and for railway to even parse logs you need to log unbuffered to stdout / stderr.