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
The tracing instrumentation brings the OpenTelemetry User Interaction instrumentation by default. Because of this, the tracing instrumentation also loads the OpenTelemetry Zone Context Manager.
The problem is that the User Interaction instrumentation is not bringing enough value to justify enabling it by default, especially because we also allow the users to load their own instrumentation and pass their own context manager.
Even if one passes a "hardcoded" array of instrumentation when initializing the tracing instrumentation and another context manager, zone.js is still loaded.
Proposed solution
There are a couple of solutions I have in mind:
do not embed the user interaction instrumentation in the tracing instrumentation package. Doing so would allow us to remove the zone context manager from the default configuration.
make the user interaction instrumentation optional along with zone.js context manager. If you choose this path, be sure to load the due using dynamic imports rather than a sync import in order to avoid zone.js from being initialized.
Context
The text was updated successfully, but these errors were encountered:
I like the idea. Currently I'm more into your first proposed solution since dynamic import() is a relatively new feature and my not work on older browsers.
Description
The tracing instrumentation brings the OpenTelemetry User Interaction instrumentation by default. Because of this, the tracing instrumentation also loads the OpenTelemetry Zone Context Manager.
The problem is that the User Interaction instrumentation is not bringing enough value to justify enabling it by default, especially because we also allow the users to load their own instrumentation and pass their own context manager.
Even if one passes a "hardcoded" array of instrumentation when initializing the tracing instrumentation and another context manager,
zone.js
is still loaded.Proposed solution
There are a couple of solutions I have in mind:
zone.js
context manager. If you choose this path, be sure to load the due using dynamic imports rather than a sync import in order to avoid zone.js from being initialized.Context
The text was updated successfully, but these errors were encountered: