Logs Are Good, Actually
summary
Argues that plain logs remain essential: uses flight timestamps, local weather, conference GitHub history and text messages to reconstruct a real scheduling incident, and traces the word “log” to the chip log and log line sailors used. Notes 40% of talks about distributed tracing at Monitorama but shows traces are just structured log lines with a parent ID. Gives operational detail: one site emits 127 log lines per page load, ran workshops to curb debug noise, and contrasts metrics (regular scrapes) with intentional, high-retention logs for known unknowns.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 1:00The value of logging
- 6:30The history of logbooks
- 12:41Modern logging relevance
- 17:20Logs as intentional messages
- 20:29Q&A and concluding thoughts
related talks
29mAre logs a software engineer's best friend? Yes - follow these best practices
30mLogging Rethought 2: The Actions of Frank Taylor Jr.
36mBeyond grep: Practical Logging and Metrics
05mLogging is a Team Sport
26mWhat every developer should know about logging
21mLOGS. HOW DO THEY AFFECT ON MY LIFE?
23mTopics of Interest: Five philosophies to building better application logs
10mStructured Logging and You