It would be really nice if non-erlang-savvy administrators could easily look at the error reports written by the error logger handler log_mf_h. Especially because the zotonic.log and sasl.log files are overwritten after a restart. The reports in log_mf_h are crash protected.
Now you can access them like this:
A (simple) browser interface would be perfect.
It won't be /that/ simple, since you need to capture the io output from rb to push it to a page.
That, or have rb redirect it's output to a file, and cat that to the page (rather ugly solution, imho).
A cleaner solution would be to simply copy the rb code for parsing the log files directly into a zotonic module (or model).
I've looked at the first approach, redirecting the io. That's actually quite doable. I've begun work on a mod_io_server, which will bridge the IO protocol and signals (from mod_signal).
Didn't look at it yet. I was hoping, ehh no expecting, the parsing code from rb would be exposed already.Copying and pasting code doesn't sound very modular.
Wow, but mod_io_server sounds really cool and would work for a lot more.
Yeah, I was expecting to be able to get the report list from rb too... but no :/
Having io bridged to signals means we can implement our own web page based erlang shell... :)
Which I've been thinking about too, for a while...
Pushed my initial, only compiled, mod_io_server module to my fork.
More to follow... but not tonight ;-)
It is now capturing io output, sending them on as put_chars signals!