Really interesting because we considered eBPF when making this but started with OpenTelemetry (for various reasons, but mostly its increasing adoption). We stil

Really interesting because we considered eBPF when making this but started with OpenTelemetry (for various reasons, but mostly its increasing adoption). We still might incorporate eBPF if it adds value. OpenTelemetry does need to instrument each service in your env (at least anything you want to make assertions on, you can also start with a subset). That said, they have an incredible community and have made installing it in Kubernetes very simple. The "Open Telemetry Operator" has auto-instrumentation for Node, .Net, Java, Python. So its very easy to add (and gives you lots of value in terms of observability in general). We chose JS and Jest for our testing framework (again because of popularity) but the trace data produced by Otel is framework/language agnostic, so it could really have been anything. And as you said, adding functionality is just a matter of writing more assertion adapters for different protocols. Its pretty straight forward, and we welcome any contributions.