Observability Ecosystem in Kubernetes
summary
Claims that instrumentation via OpenTelemetry plus collectors lets teams swap backends without code changes and demonstrates it by deploying an OpenTelemetry Helm demo to EKS 1.27 with multi‑language microservices. Uses Prometheus for metrics, Jaeger for traces and Grafana dashboards; the demo shows CPU/memory, latency, error‑rate and end‑to‑end spans across services. Notes CNCF landscape counts ~90 monitoring tools and ~21 logging tools and contrasts OpenTelemetry with eBPF as an alternative.
AI-written summary · about
chapters (17)
- 0:00intro
- 0:27preamble
- 1:02about jhonnatan
- 2:05observability ecosystem in kubernetes
- 2:25table of contents
- 2:47kubernetes architecture
- 6:23observability
- 7:54o11y golden angle
- 9:51why observability
- 12:19instrumentation
- 14:36cncf - how they are
- 15:40cncf cloud native interactive landscape
- 17:25open source tools
- 20:23o11y on kubernetes
- 21:29demo
- 44:41brief resume
- 45:24thank you
related talks
28mImplementing Observability in Kubernetes
34mKubernetes Observability with OpenTelemetry
45mFrom k9s to OpenTelemetry: A guide to observability for your apps in K8s
28mImprove Monitoring and Observability for Kubernetes with OSS Tools
50mOpen Telemetry: The Rise of Open Standards in Observability
35mOpenTelemetry for Busy People
42mOpen Source for Better Observability
20mObservability and Open Telemetry