Observability in WebAssembly
dev.dylibso.com
Observability in WebAssembly
1–10 of 33 posts
Re: Observability in WebAssembly
#2Re: Observability in WebAssembly
#3It looks like there is also (limited?) support for tracing functions and allocations in WASM binaries you didn't compile. I'm looking forward to trying this out!
Re: Observability in WebAssembly
#4Re: Observability in WebAssembly
#5Was just thinking of something like this last night. Now, wonder if I can compile JS and automatically wire up apm for all spans.
Re: Observability in WebAssembly
#6Was just thinking of something like this last night. Now, wonder if I can compile JS and automatically wire up apm for all spans.
Re: Observability in WebAssembly
#7I wonder how well (or if it's even possible?) to pair this with hosted WASM runners (like CloudFlare Workers, or Fastly Runners, etc.). It looks like there is also (limited?) support for tracing functions and allocations in WASM binaries you didn't compile. I'm looking forward to trying this out!
Re: Observability in WebAssembly
#8I wonder how well (or if it's even possible?) to pair this with hosted WASM runners (like CloudFlare Workers, or Fastly Runners, etc.). It looks like there is also (limited?) support for tracing functions and allocations in WASM binaries you didn't compile. I'm looking forward to trying this out!
Yes, it should work in Cloudflare, you'd just need to use the JS adapter for whichever APM you use (Datadog, Honeycomb, Lightstep w/ more coming soon). The library provides import functions you pass into your module instance, and as long as the Wasm was instrumented before you deploy the Worker, you should have no issues. Please let us know if you hit any though!
Re: Observability in WebAssembly
#9Was just thinking of something like this last night. Now, wonder if I can compile JS and automatically wire up apm for all spans.
I do have some experimental code working with QuickJS that does this. Feel free to reach out of if you're interested in trying it out or start a discussion https://github.com/dylibso/observe-sdk/discussions
Question: are you wiring it up like how APM is wired up in JVM applications or what exactly are you doing? Does it effect stack trace outputs or leave those alone?