Hello Railway team

First of all, thank you for building such a great platform — we’ve been using Railway actively to deploy our AI product, and overall the experience has been smooth, fast, and developer-friendly.

However, as our app grows and we continue releasing new features, we’ve been running into a serious challenge with log management and debugging efficiency.

When users report bugs right after new features go live, it’s extremely difficult to identify which specific routes or functions are failing, because the current log stream is too mixed together.

At the moment, the Logs view doesn’t support effective route-based grouping or filtering — everything appears in one long flat stream.
Even with search, it’s hard to isolate logs for specific routes like:
/ai-video, /video-prompt, , etc.

It would be amazing if you could take inspiration from Vercel’s route-based log filtering UI — that kind of structure would massively improve the speed and clarity of log investigation and debugging.
For fast-moving AI apps like ours, this could save hours every day.