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
In OpenCensus Web, we developed fully automatic tracing of user interactions such as click events. This worked by monkey-patching the Zone.runTask function (and other Zone functions) to intercept events (code link). Then when a click event occurs, we would start a new tracing zone (equivalent to a scope in OpenTelemetry) and then wait for that zone to become "stable", that is to finish all tasks that it spaws besides setInterval periodic timers.
@obecny what would you think about porting this functionality to OpenTelemetry as a new plugin e.g. UserInteractionPlugin or similar?
It would give people the option of getting started quickly with OpenTelemetry since they would get nice spans for their click events without having to do any manual instrumentation besides enabling the tracer and plugin.
The text was updated successfully, but these errors were encountered:
In OpenCensus Web, we developed fully automatic tracing of user interactions such as click events. This worked by monkey-patching the Zone.runTask function (and other Zone functions) to intercept events (code link). Then when a click event occurs, we would start a new tracing zone (equivalent to a scope in OpenTelemetry) and then wait for that zone to become "stable", that is to finish all tasks that it spaws besides
setInterval
periodic timers.Here's a (doc about its automatic tracing algorithm).
@obecny what would you think about porting this functionality to OpenTelemetry as a new plugin e.g.
UserInteractionPlugin
or similar?It would give people the option of getting started quickly with OpenTelemetry since they would get nice spans for their click events without having to do any manual instrumentation besides enabling the tracer and plugin.
The text was updated successfully, but these errors were encountered: