Description

In this part we'll highlight the relevance of having good quality logs that are easy to understand by both humans and machines. We'll describe the properties good logs must have (relevant contents, unambiguous timestamping, easy classification, integrity...), and the existing tools designed to meet these requirements, with examples for both developers (what and how to log) and system administrators (what to do with those logs). Real-world examples of good and bad practices will be shown, together with some ideas for improvement.