Direct Logger output to Nerves RingLogger and output log messages via the phoenix application

[tmecklem]

The nerves-project/ring_logger project allows the console log to be replaced by a ring buffer backed logger. It can be attached to any output, and could be passed down to the web ui via phoenix channels. This needs a little bit of work but should be fairly straightforward and low difficulty.

This is necessary for understanding what's happening in the oref0 calls over time without the need to connect to the console via serial.

Key points of what's involved:

• Add ring_logger to fw mix.exs and configure via https://github.com/nerves-project/ring_logger#configuration
• Build Phoenix channel to send RingLogger logs down to client.
• Build new log page in app to display logs and link from home page

[David-Gil]

I'm beginning to think that RingLogger is actually not what we need.
I think that we need something that permits custom handlers.
See the section about custom handler:
https://github.com/elbow-jason/slogger

[David-Gil]

I have also found this library, that forwards Logger events to RabitMQ: https://github.com/duartejc/rogger/blob/master/lib/rogger.ex

[David-Gil]

After studying the code from RingLogger, I've found out that RingLogger.Client is the key. It has the API needed to interact with RingLogger. #17 integrates a copy of RingLogger.Client and adapts it to send logs to the client via channels.