observe-sdk
observe-sdk copied to clipboard
dylibso
Continuous runtime observablity SDKs to monitor WebAssembly code.
Related to https://github.com/dylibso/observe-sdk/pull/48, when we encounter situations that don't really make sense we should have a pattern in place to log some information and if in some operational mode for...
We should have some tests. Probably a few unit tests for the adapters and something similar to the rust integration tests.
`wasmtime`, `serde`, etc could all probably use less strict versions to increase compatibility across variety of end-user codebases. We should look at the "oldest" versions of these that support our...
The shutdown methods (e.g. https://github.com/dylibso/observe-sdk/blob/main/rust/src/adapter/otelstdout.rs#L97 ) should wait on the runtime instance to close it's side of the event channel. This does get tricky because we don't have a way...
See: https://github.com/dylibso/observe-sdk/blob/main/rust/src/adapter/otel_formatter/mod.rs#L33C1-L38 If it makes sense to go more generic than `serde_json` then let's do it, but for this adapter we at least need to support json, so the `serde_json`...
Now that the SDK is not tied to the Rust OTel tracers, we should be able to convert the SDK to use `std::time::Instant` without issue.
Just as we have a re-usable OTel JSON formatter in Rust, we should support it in Go. This will act as the basis for other adapters to wrap the formatter.
On my machine `many.rs` never prints 250 times, usually it only print 200 times. However, it seems to work most of the time on CI. ``` test tests::integration_many ... FAILED...
The testing situation is currently grim, mostly done by hand. A first start is to unit test the individual modules. We also need to simplistic and well understood modules that...