While sending debug and other information out to the console is popular and easy, chances are that it becomes confusing and chaotic beyond a certain complexity. This includes the lack of a standardized date/time or origin class or inconsistent formatting, making it hard to trace an execution path through the system. Moreover, recent systems focus on logs as an additional source for information: how many users did we serve each hour of the day? Where did they come from? What was the 95th percentile response time?
Due to printing constraints we had to replace the original emoji with their names. Check out the GitHub repository for this book for the full version.
These questions can be answered with diligent logging using a framework that provides consistent and configurable output that can be easily parsed and shipped to a log analytics service. Let...
