-
Notifications
You must be signed in to change notification settings - Fork 516
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
ref(otel): Remove autoinstrumentation #3239
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #3239 +/- ##
==========================================
- Coverage 79.76% 79.72% -0.05%
==========================================
Files 133 132 -1
Lines 14313 14237 -76
Branches 3012 2997 -15
==========================================
- Hits 11417 11350 -67
+ Misses 2074 2065 -9
Partials 822 822
|
didn't we want to keep the distro setup for later? |
The distro setup mostly makes sense if we're using OTel's autodiscovery of instrumentation packages. But since we now want to enable integrations one by one explicitly, we can get rid of the distro stuff. (It also wasn't a "real" distro in the sense of how it should be used. So all in all better to get rid of it to not confuse people.) |
Removing experimental OTel autoinstrumentation since we want to focus on getting basic OTel support right. Once we're confident that our instrumentation works correctly with OTel, we can focus on adding OTel integration packages.
We can reuse some stuff this PR removes then, if necessary.
I've kept the basic skeleton and an example with Django for later to have it in place once we start enabling integrations one by one.
Closes #3238