Ignite: Bulletproof Logging
summary
Advocates writing structured logs and shows how to do it: write JSON logs directly with fields for request, status, URL, hostname and separate event timestamps from ingestion time. Use levels (error/info/debug), include inputs and outputs, keep consistent IDs and names, and avoid logging in ways that throw. Add correlation/request ID tracing (Zipkin style) to tie requests across services, build dashboards with ELK Graylog Splunk and set alerts on thresholds, and maintain the aggregator so logs aren’t lost.
AI-written summary · about
chapters (4)
related talks
29mAre logs a software engineer's best friend? Yes - follow these best practices
30mLogging Rethought 2: The Actions of Frank Taylor Jr.
10mStructured Logging and You
38mLogging as a Painkiller
06mIgnite Monitoring the right way
55mBeginner's guide to observability
39mFast log management for your infrastructure
36mBeyond grep: Practical Logging and Metrics