Elevator Pitch
Sure, we’re told actionable, parsable logs are important. But what does that mean? How has that guidance changed? Experiment with different log formats, see how machines parse logs, and discuss best practices for logging. After all, a good log helps the next person, and that might even be you.
Description
Logging is deceptively simple. You import a library, pass strings to it, and BAM you have logs. However, do you know how to write machine-parsable logs? Do you know all of the different log levels and why you need them? What does current logging best practices look like? Logging is an underutilized tool in the developer’s toolbox, and it is often misunderstood as just another unnecessary debugging tool. In reality, logging is a boon to the people who will be working on a system later down the line, and making fantastic logs really is a team sport.
In this talk, we’ll review why logs are important, log levels and types, and common misconceptions around logging. We’ll discuss the difference between text-based logs and structured logs; the big takeaway will be understanding that the true shift in logging from text-based logs to structured, machine-parsible logs is all about a change in thought: Machines are now the primary user of logs instead of human beings. Finally, we’ll review a practical framework for adding the necessary logs to an application that doesn’t have sufficient logs.