2 months ago
We're facing an issue in our production stack where logs don't get transported from Railway into Grafana Loki through the use of the Locomotive service (https://github.com/brody192/locomotive). Locomotive doesn't recognize/pull new logs from the other services anymore for the past week or so. I thought that maybe the latest new version of Locomotive (v0.6, released last week) broke something so I went and forked v0.3 cause I don't remember having any issues with it. But to no avail, the result is the same, which makes me believe that the issue isn't with Locomotive but rather something in Railway, some mechanism that it was crucial for Locomotive to function properly, and that mechanism has been removed by Railway in the past week or so. Can we please get an update as to what could be the culprit here? In the community Locomotive is still the recommended way of transporting logs to other platforms so I don't want to start building a custom solution just yet until I get a clear answer from you. Thanks.
Attachments
6 Replies
2 months ago
I will look into this, I'll follow back if I need any more information, or if I have information to share.
2 months ago
You should be good now. We raised your limits used to control the concurrent calls to get the deployment logs.
2 months ago
No problem!
a month ago
Hey Brody,
I'm facing the same issue with my locomotive deployments, is there anything we can fix ourselves on this?
solarnz
Hey Brody, I'm facing the same issue with my locomotive deployments, is there anything we can fix ourselves on this?
a month ago
Open your own thread and link the affected workspace/service.
Status changed to Solved medim • about 1 month ago