-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Blazor WASM #170
Comments
Tentatively adding to our GA milestone for now. We'll need to look into if we need to add the right stuff only in this SDK distribution, or also/only in the upstream vendor-neutral SDK. Either way it shouldn't be a terribly large lift, just requires some investigation since Blazor WASM projects are a little special w.r.t. dependencies. |
Plopping this link here: open-telemetry/opentelemetry-dotnet#2816 There are likely to be other issues with blazor-wasm even when an upstream fix lands and we take it. So while we should be able to make our SDK distro work with blazor-wasm, there may be further caveats. |
@cartermp Awesome, I'll check it out soon! |
Yeah, another quick update:
All-in-all, I'd say Blazor WASM isn't quite ready as an application type for OpenTelemetry just yet. We did work on our end to ensure that you can indeed use our SDK distribution with a Blazor app, but these issues in Blazor are unavoidable for now. If you're interested in setting up some more machinery, through the magic of JS Interop you can actually configure an app to send to honeycomb with this project: https://github.com/martinjt/otel-blazor-exporter But this is the experimental realm, so we're likely to consider our SDK as GA without a good end-to-end experience for Blazor WASM. |
Hello!
I'm working on multiple Blazor WASM applications expecting to go live mid-year and I would love to use Honeycomb.oi as a collector. Unfortunately, there's no runtime pack for it.
Is this something that would be considered?
Thank you!
The text was updated successfully, but these errors were encountered: