Blazor WebAssembly (WASM) applications run entirely inside the user’s browser. Because of this, Dynatrace OneAgent cannot instrument them—there’s no server‑side runtime for the agent to attach to. As a result, OpenTelemetry is currently the only practical way to collect observability data from WASM apps. (AKS WASM node-pools troubleshooting - Dynatrace Community)
I found an example OTEL setup for Blazor WASM on the New Relic site: (https://newrelic.com/blog/apm/how-to-observe-your-blazor-webassembly-application-with-opentelemetry-...)
This approach works, but it exposes OTEL tokens in the client‑side code, which we want to avoid if possible.
So my questions are:
Is there a recommended or best‑practice way to instrument Blazor WASM with OpenTelemetry without exposing tokens in the browser?
Is Dynatrace working on native OneAgent support for WASM workloads?
Since we are running Dynatrace Managed, we don’t have a public OTEL ingest endpoint—should we expose one, or is there a better pattern for routing OTEL data securely?
We’re looking for guidance on the safest and most future‑proof way to handle OTEL ingestion for WASM applications in a Dynatrace Managed environment.
