Cloud-Native Observability with OpenTelemetry
summary
OpenTelemetry supplies vendor-neutral OTLP traces metrics and logs, favors a traces-first model where spans (per-request units) turn into aggregated metrics, and uses W3C trace context propagation across services. The demo is a Go gRPC app that uses grpc interceptors, batching exporters, and a Collector (use contrib or build a custom binary) to redact and route data to Jaeger or Lightstep. A notebook query groups traces by product_id and pinpoints a faulty sunglasses image path; sampling and collector processors keep load and cost manageable.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:34Why Do We Need Observability?
- 14:33OpenTelemetry-Standards and Practices
- 21:20Installing Instrumentation
- 22:11Extension Installation (Kubernetes)
- 22:31Library Installation (Go)
- 29:00Collector Installation
- 30:31Collector Configuration Co
related talks
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
37mThrough the looking glass: Effective observability for cloud native applications
35mOpenTelemetry for Busy People
20mObservability and Open Telemetry
27mEnd-to-end visibility in the cloud w/OpenTelemetry
50mGuide to Observability with OpenTelemetry
47mUsing metric and traces to diagnose our cloud-native applications
18mOpenTelemetry and Observability: What, Why, and Why Now?