Observability in WebAssembly | Dylibso Developer Sources

Dylibso gives observability SDKs for WebAssembly (Wasm), enabling steady
monitoring of WebAssembly code because it executes inside a runtime. It gives
builders with the instruments essential to seize and emit telemetry information from Wasm
code, together with operate execution and reminiscence allocation traces, logs, and
metrics.

Emit WebAssembly telemetry to many supported platforms

Whether or not you employ a managed platform corresponding to Datadog, or a self-hosted resolution
like Zipkin, Observe SDK Adapters make it straightforward to ship Wasm telemetry wherever
it must go.

See the officially supported platforms by selecting
which language library you’d use.

Why a brand new stack for WebAssembly?​

There are numerous technical and legacy the reason why current observability stacks
(brokers, tracers, collectors, and so forth) do not work in Wasm. For a high-level
understanding, we suggest studying via this weblog submit,
“Observability Challenges in Wasm”.
To go deeper, watch this talk by
our co-founder, Ben Eckel, about these similar challenges in additional element.

There are two distinct steps when utilizing the Observe SDK:

1. Including an Adapter To Your Software​

With the intention to extract telemetry information from Wasm, you should add an
Adapter to the applying the place you execute Wasm.
Select the Adapter for the platform you employ to gather & analyze telemetry information.
Adapters are code libraries, so first verify if we assist the programming
language you employ:

Inside these language sections, you’ll discover the platforms we formally
assist. Select a language above and see the choices listed. There are examples
and documentation about the way to use every of those libraries.

2. Instrumenting your code (computerized or handbook)​

To ensure that any telemetry information to be extracted, the code you wish to monitor
must ship some indicators about what it is doing. That is the place
instrumentation is available in to play. We provide two methods to instrument your code:

Automated Instrumentation​

Utilizing our computerized instrumentation instruments, you’ll be able to take a compiled Wasm module
(.wasm binary) and have it totally instrumented for operate and reminiscence
allocation tracing. This can present an in depth hint of all exercise in your
code. We suggest this for debugging your individual code, in addition to tracing Wasm
modules that you just did not compile (and thus haven’t got the supply code).

Automated instrumentation focuses on tracing solely, however this might be expanded
sooner or later.

NOTE: assist for the Part Mannequin is coming quickly. Please attain out to us
if that is one thing you want
(support@dylibso.com).

???? Learn more about automatic instrumentation

Guide Instrumentation​

The Observe API gives one other method to instrumenting your code, through the use of
our libraries instantly in your supply code earlier than it is compiled to Wasm.

At the moment, handbook instrumentation utilizing the Observe APIs is the one technique to get
logs and metrics along with traces from Wasm.

NOTE: you should utilize each computerized and handbook instrumentation in the identical code.

???? Learn more about manual instrumentation

Help​

Should you’re in search of extra assist or would love hands-on assist, we’re
blissful to be of service. We are also capable of offer you your individual offline or
self-hosted model of our computerized instrumentation instruments so you’ll be able to run
the whole lot in your individual community.

Please attain out to support@dylibso.com for extra
data.

Moreover, go to the
GitHub Discussion web page for
basic Q&A concerning the Observe SDK and associated merchandise.