Logging as a Painkiller
summary
A practical recipe: three checklists that turn logs from noise into a debugging shortcut — configure and centralize logs so every component is easily reachable, searchable, and readable; capture execution and infrastructure errors plus frontend errors, cron/job start‑success‑failure events, and custom application errors; add log‑derived alerts and simple tracing (trace IDs per request/job) so you see the call sequence. Real incident: a promoted page breaks for a subset of users because logs only said “service X failed” and “error occurred”; adding these practices prevents hours of guessing. Tooling examples: ELK / Kibana / Elasticsearch, Sentry, Datadog.
AI-written summary · about
chapters (5)
- 0:00Start
- 10:41Are my logs okay?
- 16:05Am I logging what I should?
- 27:01But that's a lot of work! Is it even worth it?..
- 34:36Tooling for smarter logging
related talks
29mAre logs a software engineer's best friend? Yes - follow these best practices
29mApplication Logging
23mTopics of Interest: Five philosophies to building better application logs
36mBeyond grep: Practical Logging and Metrics
05mLogging is a Team Sport
55mBeginner's guide to observability
06mIgnite: Bulletproof Logging
29mLogging the right way