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

Only include XHR and Fetch performance timings by default, more is opt-in. #555

Closed
codecapitano opened this issue Apr 12, 2024 · 0 comments · Fixed by #560
Closed

Only include XHR and Fetch performance timings by default, more is opt-in. #555

codecapitano opened this issue Apr 12, 2024 · 0 comments · Fixed by #560
Assignees
Labels
change Request a change of an existing feature

Comments

@codecapitano
Copy link
Collaborator

codecapitano commented Apr 12, 2024

Why

The Faro performance instrumentation processes and sends all resource entries emitted by the browsers resource timeline.
The number of entries emitted can grow very large depending on how resource heavy a web app/site is.
This can be hundreds of items and more per user session!

Most users are interested in initial load and render performance, web-vitals and xhr/fetch performance.
So we want to decrease resource consumption by only tracking the most necessary entries an make the rest opt-ing

What

  • By default only track resource entries for fetch and xhr requests
  • Allow to opt-in for more or everything
    • Should be easy to be disabled with a single setting
    • Allow to customize what entries should be included (or not)
@codecapitano codecapitano added the change Request a change of an existing feature label Apr 12, 2024
@codecapitano codecapitano self-assigned this Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change Request a change of an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant