You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ok, if an application has a problem and then you click on the link to do a "tail", you only see like 15 lines which is almost useless.
You could consider going to the stderr log file that supervisord creates, but that's owned by supervisord and I can't even read.
So here are some options to make looking at log content actually useful:
Mod supervisord to have another html link per process named "view stderr" or "view stdout" .. when clicked these would display the content of the corresponding log file on an html page
Alter supervisord to allow the user to specify on startup how many lines to pass to "tail -f" .. so when one clicks that link in the supervisord UI, you get more than the current 15 or so lines
On the html page in which supervisord shows tail's output, add an html button titled "go back more" that, when clicked, stops the tail, and restarts it, but passes it a larger number than before so more content is shown (alternatively you could have a text box there that lets the user enter how many lines they'd like to go back and see)
The text was updated successfully, but these errors were encountered:
I agree that the web interface can be improved. We have this in the TODO file already, so I'm going to close this issue for now. I've added a reference back to this issue in the TODO file for when we work on it.
ok, if an application has a problem and then you click on the link to do a "tail", you only see like 15 lines which is almost useless.
You could consider going to the stderr log file that supervisord creates, but that's owned by supervisord and I can't even read.
So here are some options to make looking at log content actually useful:
The text was updated successfully, but these errors were encountered: