Skip to content
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

Automatic instrumentation for long tasks in browser #1722

Closed
bradfrosty opened this issue Dec 4, 2020 · 0 comments · Fixed by open-telemetry/opentelemetry-js-contrib#757
Closed
Labels
feature-request up-for-grabs Good for taking. Extra help will be provided by maintainers

Comments

@bradfrosty
Copy link
Contributor

Is it applicable for Node or Browser or both

Browser

Do you expect this plugin to be commonly used

Not sure, but my application would find it useful.

What version of plugin are you interested in using

n/a

Additional context

Long Tasks are tasks in the browser that take longer than 50ms. These tasks will cause slowdowns in general interactivity of the application, TTI, and animations as they occur on the UI thread. The Long Task API has been spec'd for some time now and is supported in Chromium-based browsers presently.

I would find it useful for these to automatically traced to help find areas of the application that are definitively degrading interactivity. I would be curious to know what child operations happening within a long task span, in addition to knowing where/when the longtasks are happening most frequently.

Is there a reference you could point for the well-defined lifecycle methods**

Long Tasks can be observed with the PerformanceObserver using the longtask entryType.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request up-for-grabs Good for taking. Extra help will be provided by maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants