Using logging
Logging is the most useful form of output from your system for diagnosing issues and understanding the details of its behavior. This section considers how logs should be written so that you can use them to the best effect.
Finding “the” log
It’s vital that you get the correct information to the developer to help diagnose an issue in their code. While I always try to include the relevant information, I’ve lost count of the number of times a developer has asked me for the log. It’s a simple enough request; the only problem is the word the. Which log do they need for any given issue? Within that log, which line is the clue? Other sections of this chapter will recommend approaches to finding problems within logs; here, we consider finding the correct log in the first place.
Real-world example – Logging on dual redundant hardware
In two of my jobs, I’ve improved the presentation of logs, and in both cases, I’...
