Logging in the age of Microservices and the Cloud
summary
Modern logging moves from SSH and tail to centralized structured logs stored as JSON, decoupling storage from presentation so raw fields remain queryable. Use an MDC or propagated request-id across services to trace a request end to end. Prefer managed collectors over DIY unless traffic exceeds extreme levels — CloudWatch comfortably handles 15,000 messages/sec per instance in practice. Standardize keys and values, tune retention to balance cost and usefulness, and capture context around errors rather than only severity.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:30The good old days of logging
- 3:20The cloud
- 4:03Why are we logging
- 6:03Capturing log information
- 6:35Map diagnostic context
- 10:12Querying logs
- 12:52Cloud challenges
- 15:25Autoscaling
- 19:48Writing the logs
- 23:10Log retention
- 24:47Log messages
- 28:12Distributed system
- 28:35Trace request flow
- 31:39Query logs
related talks
39mObservable microservices
31mPast, Present and Future of Microservices
28mSurviving in a Microservices Environment
24mMonitoring Microservices The Right Way
33mEffective observability in microservice architectures
04mObservability in micro-service architectures
31mHundreds of Microservices without breaking your APIs
52mSurviving in a Microservices Team
