ADR - Logging and Analytics

[EuanScott]

While features are being worked on, an engineer should have a standard way of working logging information. This can prove especially helpful when debugging the code. Create a standard library and format for how best information can be logged.

In some instances, when a specific type of error occurs, we may also need to log some kind of analytics event in order to monitor these. Investigate which analytics tool would best suit our needs.

[EuanScott]

Do we want to have a single AppLogger, which internally calls analytics/crashlytic? This would be based on the type of logger being called (info vs warning vs error).

Unknowns

1. Will we need a custom analytics and crashlytics service if we're doing this?
2. How do we want to "collect" logs to send only when a failure occurs?