Are logs a software engineer's best friend? Yes - follow these best practices
summary
Shows that logging actually shortens MTTR with concrete examples: a 403 traced to a changed OAuth key, memory unexpectedly >512 MB causing pod kills, and promise values revealed only after logging. Recommends structured JSON logs, severity levels, request IDs for distributed tracing, masking sensitive fields with regex, and choosing libraries like monolog or Winston. Demo uses Laravel with channels shipping logs to Logentries and Stackdriver on Google Cloud Run, and suggests ELK/Graylog or SaaS alternatives.
AI-written summary · about
chapters (4)
related talks
38mLogging as a Painkiller
27mLogs Are Good, Actually
30mLogging Rethought 2: The Actions of Frank Taylor Jr.
26mWhat every developer should know about logging
06mIgnite: Bulletproof Logging
05mLogging is a Team Sport
23mTopics of Interest: Five philosophies to building better application logs
36mBeyond grep: Practical Logging and Metrics