oxidized-web

oxidized-web copied to clipboard

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.

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. We'd need to revert to local logging to guarantee access there.

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: syslog: true file: /tmp/poop

or

log: /tmp/poop syslog: true

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.