Provide logging functionalities for the chain nodes

[fkleedorfer]

From the specs: "Provide logging functionalities for the chain nodes; you should be able to show which messages have been routed through/by a chain node."

IMHO, showing a log file is a little lame for the presentation. Suggestion: we implement a VERY simple webpage on the chain node that shows a list of messages that were routed (chainid, sender, recipient)

Agreed?

[IdealChain]

If the webpage is very simple, where is its advantage over the console output? It requires a step more (looking up port, opening browser) for the user.

[fkleedorfer]

I thought about an index page on the directory node with a list of chain nodes with links to their index pages, and a list of recently routed messages on the chain node. Later we could add buttons for simulating errors or even stopping the chain node to show the resilience of the system.

[fkleedorfer]

I thought about an index page on the directory node with a list of chain nodes with links to their index pages, and a list of recently routed messages on the chain node. Later we could add buttons for simulating errors or even stopping the chain node to show the resilience of the system.

[IdealChain]

Ah, that sounds like a cool idea indeed.

We should make sure that the Console logging prints the required info too though, in a clear fashion and without too much noise in the default loglevel (INFO).

[fkleedorfer]

that's right - I added an issue for that #40

[fkleedorfer]

Done. look at http://[directorynode-ip]:20141 and follow the links