OTel Me About It: Latest Updates in WASI OTel
summary
WASI OTel defines a WASI interface that lets WebAssembly components call OpenTelemetry SDKs and stream span lifecycle events to the host so host operations reparent correctly, demonstrated by a Spin demo that shows six spans stitched into one distributed trace and working logs and metrics (metrics demo has local hiccups). Guest SDKs exist for Go Rust and TypeScript, hosts run in Spin and wasmCloud, the tracing path uses a streaming start/end protocol and JSON for AnyValue. WASI OTel is in phase two and the demo uses Spin.
AI-written summary · about
chapters (18)
- 0:00Introduction to WASI OTel
- 1:23Debugging WebAssembly applications challenges
- 2:29Three pillars of observability
- 4:54Why OpenTelemetry for WASM
- 6:20HTTP telemetry limits in WASM
- 8:31WASI OTel solves observability gaps
- 9:55Virtualizing telemetry interface
- 10:37Live demo of WASI OTel
- 14:12Deep dive into WIT interface
- 17:46Handling WIT data types
- 18:48WASI OTel status and implementations
- 19:51Future roadmap and language support
- 20:52Long-term observability vision
- 23:18Call to action and community
- 23:59Q&A: Interfaces vs OpenTelemetry
- 25:03Q&A: WASM plugins and telemetry
- 26:06Q&A: WASI OTel component composition
- 27:30Q&A: Telemetry interface virtualization
related talks
28mUnlocking Observability in WebAssembly with OpenTelemetry
35mExploring the Landscape for Open Telemetry for Wasm
27mObserving the Future: Embracing OTEL in WebAssembly
25mObservability at the Edge: Instrumenting WebAssembly with OpenTelemetry
32mThe Amazing Trace: Enhancing Distributed WebAssembly With OTEL- Brooks Townsend
30mOTel Meets Wasm: Rethinking OpenTelemetry Collector Extensibility
38mTaking WASI-Cloud-Core for a Spin
28mThe WASI OS - Isolation with Communication, Wasm style