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
I am suggesting a new feature, not asking a question
Description
Proposed Solution
Expose a new route from web.py/log, which will return all of the applications logs in JSON format
Add a new tab to the modern web UI that will fetch and display the logs
Implementation
There are two possible implementations:
Using logfiles:
The logs are outputted to a file when the --logfile option is set
The /log resource can then read from this logfile and return the output in JSON format
Using a new handler:
Add a custom log handler that keeps track of all application logs
The /log resource would then read from this custom handler
The one complexity will be if we want to display worker logs as well we will need to setup new event handlers so that the worker can report their logs to master
The text was updated successfully, but these errors were encountered:
Second option sounds better to me. Perhaps we need to limit the amount of data held in the buffer though (something like 1000 log messages could be a reasonable default)
Worker logs would be nice too of course, but that can be step two.
Prerequisites
Description
Proposed Solution
web.py
/log
, which will return all of the applications logs in JSON formatImplementation
There are two possible implementations:
--logfile
option is set/log
resource can then read from this logfile and return the output in JSON format/log
resource would then read from this custom handlerThe one complexity will be if we want to display worker logs as well we will need to setup new event handlers so that the worker can report their logs to master
The text was updated successfully, but these errors were encountered: