You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great work on this library so far.
I know implementing Opentelemetry is no small task.
So given the (presumable) long roadmap ahead to get all otel features implemented natively in Dart, would it not be a feasible solution to have FFI dart bindings for the native C++ otel implementation?
Using Opentelemetry on serverside application (Serverpod) should allow us to do this.
Or am I oversimplifying this?
The text was updated successfully, but these errors were encountered:
Firstly, I'll admit I'm unfamiliar with FFI bindings.
If the goal is to write dart code, specifically dart code instrumented with otel dart, but have the underlying implementation of the otel dart api call otel C++ bindings, then that seems like a reasonable task. This would be a second otel dart sdk implementation. This seems possible and reasonable but no small task to implement or maintain.
Yea I'm also not too familiar with FFI.
But looking at the examples from Dart website we would need to create Dart implementations of the public C++ headers.
With the C++ otel implementation being fully featured if these header bindings could be done (agreed, no small task) we could have fully featured otel implementation for dart using native implementation underneath.
Maybe someone with more FFI experience can comment on this
Great work on this library so far.
I know implementing Opentelemetry is no small task.
So given the (presumable) long roadmap ahead to get all otel features implemented natively in Dart, would it not be a feasible solution to have FFI dart bindings for the native C++ otel implementation?
Using Opentelemetry on serverside application (Serverpod) should allow us to do this.
Or am I oversimplifying this?
The text was updated successfully, but these errors were encountered: