Modern Observability: Making OpenTelemetry work for you
summary
Modern observability here centers on a concrete workflow: instrument once with OpenTelemetry and run telemetry through Weaver (open source, written in Rust, containerized) which generates SDK constants, opinionated helpers, and Markdown docs via MKDocs and performs live validation by ingesting duplicated data from the OpenTelemetry Collector. Weaver flags undeclared attributes, namespace collisions, and deprecated fields, produces attribute registries and codegen, and is already used at scale in large organizations to make AI context and debugging actually useful.
AI-written summary · about
chapters (10)
- 0:00Modern observability intro
- 3:40What observability means
- 8:19Telemetry data types
- 11:56Why OpenTelemetry matters
- 14:49Telemetry data strategy
- 20:03Automating with Weaver
- 26:30Weaver and Aspire demo
- 33:08Live validation demo
- 39:47Conventions dos and don'ts
- 43:20AI telemetry docs
related talks
23mObservability by Design: Leveraging OpenTelemetry Weaver To Take Control of Your Observability
35mOpenTelemetry for Busy People
18mOpenTelemetry and Observability: What, Why, and Why Now?
37mObservability For You And Me With Opentelemetry
20mObservability and Open Telemetry
20mKeynote: (Open)Telemetry Makes Observability Simple
30mAuto-generated coherent Observability
22mOpenTelemetry – An Observability Framework for Cloud-Native Software