Repository navigation
New log viewer makes structured logs hard to follow #12176
Replies: 3 comments 1 reply
|
Hi, I came here by being pointed to this discussion from the discord community. I feel a lot of UX pain with the "Runtime logs" page and would like to propose changes to this page to improve on it. I don't mean to insult the making of this, I might sound a bit harsh in how I say what I dislike here, but the accordion is just not the right fit for multiple services/containers with logs. Also having to scroll the page and logs if I open more than one feels horrible. Services of production and preview deployments are mixed without sorting. Finding the right service name is not easy due to all the random suffixes added. The log viewer itself - as @FelipeSharkao already described, is in grid mode by default which i dont see the point in really. When I read the logs, I need the space to show me as much log lines as possible. I had an Agent do several iterations with me until I arrived with these UI changes, which was the quickest way for me to visually share my ideas. Let me know what you think and I hope to hear suggestions and additional ideas as well as critique.
|
|
My changes can be found here: main...PhilippMolitor:coolify:cursor/runtime-logs-selectors-a2ba |
|
Thanks @PhilippMolitor for the suggestions, it will keep pushed to 4.5, releasing soon. I will change a few minor things but I really like it. :) |





Uh oh!
There was an error while loading. Please reload this page.
The new log viewer collapses white space and adds a ton of padding, making structured logs (those that rely on indentation and alignment) really hard to follow
It seems to expect my logs to be structured in a specific way (like json), but my application was not built with coolify in mind. Is there an option to revert to the simpler log viewer (the same that deployment logs use)?
All reactions