How To Observe Your Blazor WASM With OpenTelemetry And Real User Monitoring?
summary
Shows a working .NET Blazor WebAssembly sample that has backend tracing exported via OpenTelemetry OTLP export to New Relic, with clear steps for installing NuGet packages and running an OpenTelemetry collector. Compares auto vs manual instrumentation with code snippets that add activities and custom attributes so backend spans break down into real subspans. Demonstrates the front end limitation that browser WASM cannot directly send OTLP, and the practical workaround of injecting a New Relic Real User Monitoring JavaScript snippet to capture browser metrics and correlate traces.
AI-written summary · about
chapters (10)
- 0:00Blazor WASM monitoring intro
- 2:54What is Blazor WASM
- 5:20OpenTelemetry fundamentals
- 7:07Instrumenting .NET backend
- 12:45Manual instrumentation
- 15:36Monitoring Blazor WASM frontend
- 17:48WASM telemetry limits
- 18:09Real User Monitoring
- 20:42Observing WASM components
- 23:12Q&A
related talks
01h 00mPractical OpenTelemetry for .NET
25mObservability at the Edge: Instrumenting WebAssembly with OpenTelemetry
51mHands-on Development Experience Using wasm Blazor
35mExploring the Landscape for Open Telemetry for Wasm
01h 01mPractical OpenTelemetry in .NET 8
30m"Observability for the Front End"
40mObservability for All!
27mObserving the Future: Embracing OTEL in WebAssembly