-
Notifications
You must be signed in to change notification settings - Fork 237
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
Add performance.mark and performance.measure for performance browser tool integration #617
Comments
(I'm Todd's colleague on the Microsoft Edge team. 😃) At a minimum, it would be nice if performance.mark/performance.measure could be enabled via query parameter flags or some other mechanism. We rely on marks and measures when doing performance trace analysis. |
New extension created to provide this capability |
Waiting for NPMJS Admins to create the new package name so we can publish, this will also be released as a self contained CDN downloadable component, which is a separate deployment than the NPM deployment |
Now also published to NPM |
v2.7.0 is not fully deployed to NPM and all CDN endpoints |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Various performance tools for all major browsers including Edge and Chrome can display performance.mark and performance.measure data in the default tooling. In addition to this, the various native profilers used by the teams that build those browsers allow these events to be viewed.
I'm a performance expert working on the Microsoft Edge team. When working with teams that use AppInsights to measure their performance, we have found that those teams have to do additional work to add performance.mark/measure to their code.
In an ideal world, App Insights would emit these events allowing those websites to easily describe their start/end events that they'd like us to analyze.
The text was updated successfully, but these errors were encountered: