Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Observability in WebAssembly

dev.dylibso.com

Post reply on HN
Print view View original

11–20 of 33 posts

Re: Observability in WebAssembly

#11

Post by bhelx »

_boffin_ wrote: post #9
bhelx wrote: post #5

Earlier quoted context omitted.

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

I’ll be reviewing. 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?

I have an instrumented version of QuickJS that can be used in the javy toolchain: https://github.com/bytecodealliance/javy

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.

Re: Observability in WebAssembly

#12

Post by nilslice »

lukevp wrote: post #10

This is by the same team behind Extism, a WASM plug-in library implemented in multiple languages. I’ve been active on their Discord and they’ve been really awesome and supportive of any questions I have. I’m excited to see where they go with this observability SDK. WASM has a major usability problem right now, and we need things like this and Extism to make it smoother to produce and consume wasm programs!

you're too kind! and excited to see your WebAssembly projects here on HN sometime too :)

Re: Observability in WebAssembly

#13

Post by naillo »

What a crazy choice of background color. On the other hand it kinda signals that the developers themselves designed it which is generally a good sign of other characteristics of a project.

Re: Observability in WebAssembly

#14

Post by nilslice »

naillo wrote: post #13

What a crazy choice of background color. On the other hand it kinda signals that the developers themselves designed it which is generally a good sign of other characteristics of a project.

i'm the developer (non-designer) responsible for this, and dying laughing, so thank you!

Re: Observability in WebAssembly

#15

Post by _boffin_ »

bhelx wrote: post #11
_boffin_ wrote: post #9

Earlier quoted context omitted.

I’ll be reviewing. 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?

I have an instrumented version of QuickJS that can be used in the javy toolchain: https://github.com/bytecodealliance/javy 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…

Awesome work and looking forward to checking it out.

One thing I’m also thinking about for node and friends is looking into is using v8 profiling and seeing if I can hook up something from that.

But yeah, great stuff

Re: Observability in WebAssembly

#16

Post by syndicatedjelly »

naillo wrote: post #13

What a crazy choice of background color. On the other hand it kinda signals that the developers themselves designed it which is generally a good sign of other characteristics of a project.

lol i didnt even notice the change, just that i felt more agitated by the end

Re: Observability in WebAssembly

#18

Post by nilslice »

onemoresoop wrote: post #17
naillo wrote: post #13

What a crazy choice of background color. On the other hand it kinda signals that the developers themselves designed it which is generally a good sign of other characteristics of a project.

Somebody is a big fan of mustard

twomoresoops plz

Re: Observability in WebAssembly

#19

Post by wikiwong »

lukevp wrote: post #10

This is by the same team behind Extism, a WASM plug-in library implemented in multiple languages. I’ve been active on their Discord and they’ve been really awesome and supportive of any questions I have. I’m excited to see where they go with this observability SDK. WASM has a major usability problem right now, and we need things like this and Extism to make it smoother to produce and consume wasm programs!

Thanks Luke, we greatly appreciate your engagement and help in hardening this ecosystem!

Re: Observability in WebAssembly

#20

Post by titzer »

Great to see more focus on observability for Wasm now. This was a major impetus and still a major goal of the Wizard Research Engine, which has engine-level hooks that allow programmable instrumentation.
Post reply on HN