OpenTelemetry – An Observability Framework for Cloud-Native Software
summary
OpenTelemetry provides a vendor‑agnostic instrumentation layer that lets applications emit traces, metrics and logs to back ends like Zipkin, Jaeger, Splunk or AWS X‑Ray; traces are production ready with 1.0 traces ready, metrics are mixed by language and logs early draft remains unusable for production. A central OpenTelemetry Collector (deployable as sidecar or standalone) can receive telemetry, convert Prometheus and Jaeger inputs and forward to multiple back ends — the demo shows a Java pet‑store where a deliberate 3s bunny delay is found via SDK, annotations or auto‑instrumentation.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:41Foundation for observability
- 3:33CNCF Cloud Native Landscape
- 4:02CNCF end-user technology radar
- 5:49OpenTelemetry Reference architecture
- 8:06Open Telemetry status
- 17:11Example: Open Telemetry Collector on AWS
related talks
28mGetting Started with OpenTelemetry
20mObservability and Open Telemetry
32mOpenTelemetry feat. logs, metrics and traces
35mOpenTelemetry for Busy People
43mWhat is this OpenTelemetry thing?
30mOpenTelemetry 101
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
38mThe State of OpenTelemetry