-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose log file via web UI #3
Comments
On ruby 2.0 or older, or 1.9.3 with appropriate gem loaded it's all syslog, so we don't know where it's written, it might not be written even locally. |
You could offer local log as an option and, if it's enabled, display that. If it's not enabled, let the user know that they could do it if they wanted to in the "logs" page. |
Should we allow enabling both or just one at a time? log: or log: /tmp/poop or log: [/tmp/poop SYSLOG] |
I like the idea to allow both syslog and file simultaneously. |
Yeah we need to return file logging support. Especially for dockerized installs it's more prudent to log to file (STDOUT). |
Can the discussion of logging to a file be moved to ytti/oxidized? Once that is implemented, I can look into displaying the logs in the web UI. |
This could be as simple as offering a page that loads the log file in full and displays it via www.
If the web UI is the preferred way to interact with oxi, it should be possible to look up any errors/warnings in there, as well.
The text was updated successfully, but these errors were encountered: