-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Hello 👋 I am one of OpenTelemetry Go maintainers (https://github.com/pellared).
I started working on https://github.com/open-telemetry/opentelemetry-go-contrib/issues/4163 and I think that it may be more beneficial for the community if the ownership of OpenTelemetry instrumentation would be moved under MongoDB.
The reasons are the following:
- This is currently a more preferred way according to our recommendation
- OTel maintainers and approvers have no capacity on maintaining otelmongo instrumentation library which seems to be quite popular. More: https://github.com/open-telemetry/opentelemetry-go-contrib/issues/2834
Therefore, I am asking you could consider doing e.g. one of the following:
- Instrumenting with OpenTelemetry "natively" (without requiring the users to use an instrumentation library)
- Simply moving the otelmongo instrumentation library to https://github.com/mongodb/mongo-go-driver repository or to a new repository in https://github.com/mongodb organization.
You can look at following resources for further insight:
- https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/instrumentation/README.md#new-instrumentation
- https://opentelemetry.io/docs/specs/semconv/database/database-spans/
- https://opentelemetry.io/docs/specs/semconv/database/database-metrics/
- https://opentelemetry.io/docs/specs/semconv/database/mongodb/
I would like to collaborate and together come up with a plan that could be well received by the users of both https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo and https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/go.mongodb.org/mongo-driver/mongo/otelmongo.
- related to
-
DRIVERS-719 Client Side Support for OpenTelemetry
- Defining
-
GODRIVER-3269 Maintain otelmongo
- Backlog