555 only include xhr and fetch performance timings by default more is opt in #560
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-in
What
fetch
method orxhml-http-request
i. e.initiatorType: xmlhttprequest | fetch
Links
Checklist