News - Meet Whamm: The WebAssembly Instrumentation Framework

Every once in a while, a particularly interesting release or project is introduced at a major conference with little or no marketing backing, or by large, corporate‑like teams. At KubeCon + CloudNativeCon, Elizabeth Gilbert, a Ph.D. candidate at Carnegie Mellon University, described a project called Whamm that can really work out of the box with just one line of code. It does not replace, ameliorate, or improve existing tools and processes, but can do things that have not properly existed before. Gilbert did an excellent job describing the project she created, and it has garnered a significant number of downloads and forks following her aforementioned talk, 'Whamm: A Framework for Performant, Sandboxed Instrumentation' at the CNCF-hosted KubeCon + CloudNativeCon co-hosted event WasmCon. Whamm is designed to allow users to instrument their WebAssembly, or Wasm, applications with a programming language or code, or to program their WebAssembly applications in modules directly. With it, they can debug, monitor, etc., their applications within WebAssembly modules. Whamm was spearheaded by Carnegie Mellon Ph.D. candidate Elizabeth Gilbert during her talk at WasmCon before KubeCon NA today. This instrumentation framework for WebAssembly should attract interest and support for Wasm observability. @linuxfoundation pic.twitter.com/MZBFkfjsFu — BC Gain (@bcamerongain), Nov. 11, 2025 Originally introduced in a paper titled 'Flexible Non-intrusive Dynamic Instrumentation for WebAssembly,' Whamm is described as a framework for 'Wasm application monitoring and manipulation.' On Gilbert’s GitHub page, she describes Whamm’s instrumentation, monitoring and bytecode rewriting capabilities this way: Instrumentation: When we say we are 'instrumenting a program,' at a high level we mean we are 'injecting some code into a program’s execution to do some operation.' This definition is intentionally generic since instrumentation can really do anything we can imagine! You can use instrumentation to build debuggers, dynamic analyses, telemetry generators, and more. Dynamic analysis: A dynamic analysis is something that analyzes a program as it is executing (in contrast to a static analysis which analyzes a program that is not running). This type of analysis can gain useful insights into a program as it is able to access information that is not available statically (such as hot code locations, memory accesses over time, code coverage of test suites, etc.). Bytecode rewriting: This is an example strategy for injecting instrumentation logic into the application. It injects instrumentation through literally inserting new instructions into the application bytecode. 'Instrumentation is really a way to observe your application behavior, which is a fairly flexible enough definition to encompass all the different things. It can be observability, but it can also be used for testing use cases, such as fault injection testing,' Gilbert told me at KubeCon + CloudNativeCon after her talk. 'You can inject faults into your application to see if it’s able to handle things correctly. Instrumentation can be used to manipulate application execution as well as it’s doing.' As Gilbert explained, the main motivation for focusing on WebAssembly is language interoperability. 'Since multiple different languages can compile to WebAssembly, this is what is desired for the tooling to be really cool. If you have language-agnostic tooling, then if some new programming language comes along, if it just compiles to WebAssembly, you could get all the tools for free,' Gilbert said. 'This polyglot possibility could be really, really cool for a lot of different people. As Wasm becomes more widely targeted, if we have the instrumentation story there, then all the dev tools can be obtained for free, and the platform can hook into all kinds of different things.' The current status of the project is that it can 'do quite a few things, but there is a need to work out more use cases to make it more robust,' Gilbert said. 'The project has currently been worked on in isolation. More people, especially engineers, contributing would be 'killer' because then the work can go faster.' Indeed, I already expect to see a number of engineers looking to contribute to and benefit from Whamm.