Logging is a Team Sport
summary
Claim: logging succeeds when teams treat it as a shared engineering task rather than an individual chore. Gives a five-step, practical framework applied to legacy apps: identify inventory of logs, run a gap analysis, hold cross-team discussions to agree on company-wide standards, implement changes to update legacy apps, and continuously monitor changes for regressions. Calls out common blockers — mistaken assumptions, complacency, and resentment — and ties logging to DevOps communication so standards reduce firefighting and duplicated work.
AI-written summary · about
related talks
23mTopics of Interest: Five philosophies to building better application logs
21mLOGS. HOW DO THEY AFFECT ON MY LIFE?
29mAre logs a software engineer's best friend? Yes - follow these best practices
38mLogging as a Painkiller
27mLogs Are Good, Actually
48mI Want to See My Logs
29mCrucial Log Management Skills for DevSecOps
30mLogging Rethought 2: The Actions of Frank Taylor Jr.