Observing the Future
summary
Claims a vendor‑neutral observability stack built on OpenTelemetry agent + collector that sends traces logs and metrics into Kafka for routing and in‑flight processing and then fans out to Prometheus Jaeger Datadog Splunk or Elasticsearch. Implementation uses Kubernetes sidecars and daemonsets with a GitOps deploys sidecars workflow so instrumentation is declarative. Emphasis is on full data control parallel context propagation and cost control via Kafka high‑throughput logging and pluggable backends.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 0:45Observability challenges
- 1:06Long-term monitoring strategy
- 3:11Choosing OpenTelemetry
- 5:59OpenTelemetry architecture
- 7:21Why OpenTelemetry standard
- 9:10GitOps for OpenTelemetry
- 10:13Kafka data routing
- 11:36Real-time analytics pipeline
- 12:20Alerting and monitoring
- 12:43Closing
related talks
13mArchitecting an open observability stack
01h 02mDesigning an open-source observability stack for Kubernetes
23mWhen Kafka Goes Cloud Native: Observability That Actually Works!
46mObservability Ecosystem in Kubernetes
42mOpen Source for Better Observability
35mOpenTelemetry for Busy People
56mFull-stack observability and application monitoring with
50mGuide to Observability with OpenTelemetry