Architecture: Logging and Servicability

[matthew-chirgwin]

Issue to document how logging will work in both the client and server of the Strimzi UI, thus enabling the ability to maintain and debug the UI as and when required.

Suggestions:

• On the server side use a logging library to write to STDOUT
• On the client side, set up a/use an existing Websocket to send log messages to the server, which then appends them to STDOUT
  • These log messages from the client are enabled/disabled via query parameter in the URL. This is detected by a Logging Hook, which provides a logging calbback used in components/code on the client side, which if enabled sends the content over the web socket.
• Stretch - have some sort of ID to link/correlate server actions and client actions (eg a request for data can be tracked from initiation to response to render)