Simplifying Multi-Cloud Observability
summary
Claims a single open standard cuts multicloud observability toil: OpenTelemetry SDK replaces multiple cloud SDKs so code keeps the same namespace while adding an Azure Telemetry exporter (or AWS/GCP exporter) simply sends the same metrics to different backends. Cites 98% of enterprises adopting multicloud, and shows Grafana as the single pane of glass with Prometheus for metrics, Loki for logs and Jaeger/Zipkin for traces. Outcome: fewer SDK versions to maintain, consistent semantics, and easier on-call debugging.
AI-written summary · about
chapters (8)
- 0:00Introduction and Speaker Background
- 0:49Agenda Overview
- 1:13Understanding Multi-Cloud
- 3:35Introduction to Observability
- 5:09Challenges of Multi-Cloud Observability
- 7:15Simplifying Observability with OpenTelemetry
- 10:30OpenTelemetry Architecture and Implementation
- 13:17Conclusion and Additional Tools
related talks
46mObservability Ecosystem in Kubernetes
50mOpen Telemetry: The Rise of Open Standards in Observability
42mOpen Source for Better Observability
13mAchieving Seamless O11y Across Cloud Providers
28mOpen Source for Better Observability
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
01mObservability
