Panel: Observability
summary
Panel argues observability requires concrete tradeoffs not slogans, showing tools and limits: OpenTelemetry focuses on vendor‑neutral SDKs but not backend portability, tracing grows because microservices have thousands of nodes per transaction, sampling like one out of every 10,000 traces reconstructs metrics but breaks percentile histograms, vendors and in‑house stores face billions of metrics and real dollar costs, AI/ops and auto remediation help narrow cases but auto-remediation needs domain rules and high trust to avoid noisy 2am pages.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:09Partha
- 1:40Liz
- 2:05Stephane
- 2:37Gabe
- 2:52Richard
- 3:27Darya
- 13:00Challenges
- 15:41Cost
- 18:01Inhouse solutions
- 21:05Unified view
- 25:06Observability challenges
- 26:29AIOps
- 30:54Richards take
- 33:47Microservices
- 36:50Open Telemetry
- 42:59Autoremediation
related talks
33mCloud Native and Kubernetes Observability Panel: The State of Union
29mPanel - Observability: What's the big idea?
30mPanel: Telemetry That Matters
36mPanel Discussion: The Present and Future of Open Source Observability
36mPanel: OpenTelemetry...
33mWhat Developers Should Know About Observability
39mPanel Discussion: Application Monitoring
34mObservability 2.0: Shifting Left From Reactive Mon...
