-
Notifications
You must be signed in to change notification settings - Fork 765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move remaining instrumentation libraries to the opentelemetry-dotnet-contrib repo #5526
Labels
enhancement
New feature or request
Comments
We'll miss some extra test coverage by doing this, but that is okay, since all signals/instrumentations are stable already! |
@cijothomas - Thats a good point. I think that can be managed by upgrading the dependencies on instrumentation libraries in timely manner. |
vishweshbankwar
added
the
help wanted
Good for taking. Extra help will be provided by maintainers
label
Apr 12, 2024
1 task
vishweshbankwar
removed
the
help wanted
Good for taking. Extra help will be provided by maintainers
label
Apr 15, 2024
This was referenced Apr 19, 2024
Also, migrate the existing GitHub issues that are related to these components. |
This was referenced Apr 25, 2024
This was referenced May 6, 2024
I think this is done. |
This was referenced Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The repo currently maintains the following instrumentation libraries:
OpenTelemetry.instrumentation.AspNetCore
OpenTelemetry.instrumentation.HttpClient
OpenTelemetry.instrumentation.SqlClient
OpenTelemetry.instrumentation.GrpcNetClient
We should consider them moving all to the contrib repo and keep this repo focused mainly on core components.
The text was updated successfully, but these errors were encountered: