3 months ago
Whilst the ever evolving log facilities are appreciated, they frequently just don't work.
I'm stuck at the moment with a filter not working - all I can do is reload the page.
Frequently "view in context" doesn't work - I get greyed out logs.
I note there is a download facility - this would be optimal, except it doesn't download the ranges specified in the "filter".
If I specify 7 days, I get the last few hours.
I would much rather have no online interface and just be able to access the plaintext logs.
6a6c4123-f4c9-4c41-ba5f-c3115ddc1753
6 Replies
3 months ago
Hey, weirdly enough I've had none of the issues you described. If you could create a #🤗|feedback thread about it with videos, that would help a lot.
Also, you can export your logs from Railway to somewhere else by using and, for example, forward them to Axiom.
Thanks for the reply - only had a quick look but that seems to be a realtime log, I really just want to dump the logs really as plaintext, I suppose I could spin up something that calls an api for it, just would love to be able to grab a txt copy when needed as a one-off
3 months ago
There's a button on the interface for a one-time log dump, it won't download everything but should be enough for your use case.
Attachments
https://discord.com/channels/713503345364697088/1478045644680593438
I noted that it doesn't really work though
3 months ago
Oh sorry, I skipped that. That button only downloads the current logs on the page (if you scroll to the top, you'll see the "Load More" button). A #🤗|feedback could be created for that, but I doubt Railway would add it (it feels too specific and might be computationally heavy) but worth a try.
Using the API or Locomotive is the way to go if you really need that functionality, you could probably vibecode a CLI for it in a hour, the query is really simple:
{
serviceInstance(environmentId:"", serviceId:"") { # environment and service id can be obtained through the dashboard
latestDeployment {
id # deployment id to be passed down there
}
}
deploymentLogs(deploymentId: "", limit: 5000, startDate: "", endDate: "") {
message
attributes {
key
value
}
severity
timestamp
}
}If you'd rather just work with logs in plaintext we've been building an open-source TUI to do that - recently validated that you can stream in Railway logs to it from the CLI