-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Node]: Support otel auto instrumentation when code is bundled #10940
Comments
I can imagine so many scenarios where this esbuild plugin will break. |
For vis: I have this PR to add an esbuild plugin for this to OTel js contrib open-telemetry/opentelemetry-js-contrib#1856 |
@drewcorlin1 huh neat. Thanks for sharing. We'll definitely investigate also creating a plugin ourselves. |
Hey guys! Is there any ETA for providing the plugin for webpack/esbuild? This is still blocking us from migrating to v8 :/ |
Hey, sadly not so far! I think for now using a plugin such as mentioned/proposed by @drewcorlin1 is the way to go! |
Unfortunately it's only for esbuild, while I need to support webpack as well. |
It's in our backlog and I'll make sure we make it part of our planning! |
@mydea Any news? |
@Michsior14 you'll see it here! We haven't started working on anything. |
Problem Statement
OpenTelemetry auto instrumentation relies on
import-in-the-middle
andrequire-in-the-middle
to hook loading of modules so they can be proxied and automatically instrumented. If the code is bundled, modules are not loaded so there is no auto instrumentation.Solution Brainstorm
Using the Sentry bundler plugins, we can wrap the "loading" of modules and call the existing callbacks that hook up the instrumentation.
The text was updated successfully, but these errors were encountered: