observe-sdk
observe-sdk copied to clipboard
dylibso
Continuous runtime observablity SDKs to monitor WebAssembly code.
Via the observability workshop: if an instrumented module calls into a host function, we might lose span association if the host function makes any external calls. We may want to...
Ideally still store old namespace modules in repo in a special test data directory for testing for backwards compatibility, but out of the way for new observe-sdk users.
`corpus/02-component-instr-combined` does not build with `cargo component` `v0.8.0`.
#142 , but for the Go SDK Impossible until `wazero` support components.
#142 , but for the JS SDK maybe use [jco](https://github.com/bytecodealliance/jco)
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.58.0 to 1.58.3. Release notes Sourced from google.golang.org/grpc's releases. Release 1.58.3 Security server: prohibit more than MaxConcurrentStreams handlers from running at once (CVE-2023-44487) In addition to this...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Discover any work required to ensure compatibility of the Observe SDK with the new breaking changes introduced by OpenTelemetry. 
Working on [Updated Versioning](https://github.com/dylibso/observe-sdk/issues/143). I added deprecation warnings for the old namespace `dylibso_observe`. However, I'm not sure they are going the right place or actually making it to the observe-sdk...
Running the stdout adapter on `../test/nested.instr.wasm` can yield varying results. No triage has been done to determine if it occurs with the other adapters. One run: ``` gavin@teleporter:~/dev/observe-sdk/go$ go run...
As this check would be advisory, it is not essential for https://github.com/dylibso/observe-sdk/issues/143 and thus https://github.com/dylibso/observe-sdk/issues/142 . Work is near done on the wasm-instr side, but split off here to avoid...