Our Path to Observability
summary
The talk explains how observability helps manage rising system complexity and improve stability and team confidence. It describes an implementation using open-source tools—Elasticsearch, Prometheus and OpenTelemetry SDKs—and discusses challenges encountered and lessons learned during the rollout.
AI-written summary · about
chapters (32)
- 0:00Welcome
- 1:04What is observability
- 2:29Company context
- 3:55Growth and challenges
- 5:44Identified problems
- 8:14Responsibility shift
- 8:57Observability defined
- 10:01Observability origins
- 11:03Monitoring vs observability
- 12:05Three pillars
- 13:30Structured logs
- 15:56Log conventions
- 17:20Log tools
- 18:26Metrics and alerts
- 21:16Distributed traces
- 22:40OpenTelemetry
- 25:08OpenTelemetry Collector
- 27:14Trace tools
- 29:01Using Jaeger
- 31:06Adoption process
- 33:33Iterative observability
- 34:17Training and knowledge
- 34:58Sampling and costs
- 36:20Mindset shift
- 37:44Observability vs monitoring
- 39:08Initial recommendations
- 40:33PoCs
- 41:37Avoid vendor lock-in
- 42:19Adoption balance
- 42:39Process improvement
- 43:21Alert fatigue solution
- 45:05Current data and logs
related talks
35mObservability: Building Confidence & Answering the What, Where, How
48mObservability or How to Know the State of Your System
47mEntiende tus sistemas con OpenTelemetry
29mObservability; a gentle introduction
42mObservability can help you understand change
45mOpen Source for Better Observability
32mThe Role of Observability in Cloud Native Environments
48mAPI Observability by Design: Building Systems That Tell Their Own Stories