What every developer should know about logging
summary
Explains why logs are essential for debugging distributed Go services, shows concrete stacks: apps log to stdout then a forwarder to Logstash/Kibana+Elasticsearch or Splunk, and mentions go libraries: standard log, glog and go-kit. Recommends structured entries with request ID, timestamp, requestDelta/localDelta and service name; warns to rotate files and never log passwords or keys. Describes runtime level switching via an internal control API and log sampling every 10k–100k to cut volume while preserving signal.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:21My name is Slawosz Slawinski
- 0:43What is topic of presentation?
- 1:52Logging 101
- 9:47Logging infrastructure - applications
- 13:39Log message structure
- 18:30Logging in microservices/SOA
- 20:51Golang log libraries
- 21:50Tips and tricks
- 25:27Dapper - tracing system from google
related talks
29mAre logs a software engineer's best friend? Yes - follow these best practices
36mBeyond grep: Practical Logging and Metrics
27mLogs Are Good, Actually
21mContextual Logging for Modern Go Applications
48mI Want to See My Logs
30mLogging Rethought 2: The Actions of Frank Taylor Jr.
29mCrucial Log Management Skills for DevSecOps
06mIgnite: Bulletproof Logging