Problem/Justification
when there is an error popup if for example an app fails to start, it has a button to show the traceback of whatever program(s) had the issue, while also depending on the service it may or may not tell you the log file path to check. the traceback is not that helpful in most cases as specific lines of code within the programs dont mean much without any context or other information, it would be more prudent to show the actual logged output of the program(s) leading up to the failure.
Impact
since there is no easy gui way to access log files (other than /var/log/messages, which is what shows at the bottom of the webui if turned on), it would be much faster and more convenient for users to be able to view the logs right then and there from the error popup rather than having to switch to a shell and go from there. truncated to the relevant entries of course, not the whole giant thing.
my personal suggestion would be to change “more info” to “traceback” and also add a “view log” expander to the error popup, to not remove the traceback if it is valuable in some situations. alternatively, adding a “logs” submenu to the gui and just hyperlinking to the appropriate one would also suffice i think.
User Story
i spent quite a long time trying to figure out why a docker compose container i was trying to launch was refusing to up despite using no less than 4 different proven configurations i found online as well as trying to add/remove/alter lines i figured might be doing something weird. finally, much later than i should have admittedly, i went and checked the app_lifecycle log. turns out the issue was just that my docker registry credentials were bad (which in and of itself was weird since my username and password didnt change) and so dockerhub was returning “unauthorized” when trying to grab the images. literally never would have figured that out without the log and i never would have stumbled across the answer messing with yaml. again, should have checked it earlier, but still if i had a nice convenient button right there in the error popup that would have showed me the log right then and there i definitely would have checked it the first time and been able to see and fix the problem immediately.