Customer/support facing logging implementation

The current logging implementation is too verbose and unreadable for customers or support to make good use of it. It's very useful for developers, so we don't want to get rid of it, simply augment it with a system that can be used by more novice users.

One proposal is to leverage the existing "UI" logs which contain only a subset of the log information such as user configuration changes (bucket creation) and process failures.

The requirements for this system are that the data is exportable via text, contains enough information to be useful but not so much that it is too verbose (errors, warnings, config changes should be sufficient) and that it is easily parsable. One of the major issues with the current system is that it is very hard to "grep" for information because of the multi-line format.

Every line in the customer/support logging system should be formatted in a manner similar to:
<timestamp> <node_id>: <process_name> <process_pid> <log_level> <log message>