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!
I am one of the maintainers at SigNoz [1], an otel native open source observability platform and would love to enable our users to see telemetry data from WASM
We’ve got a ticket open on the GitHub repo to track in case you’d like to follow along. Happy to get your users supported!
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?
There are two primary goals:
1. Emit metrics directly about the QuickJS runtime similar to node metrics 2. Expose the Observe API as js bindings
With the Observe API exposed to JS, you can do manual instrumentation. I have also instrumented the pieces of QuickJS that invoke JS functions in order to automatically emit spans and it works, but still trying to fill some information gaps to make it more usable than manual instrumentation.
> 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?
I can't speak to how JVM does it, but no this does not effect the call stack.
