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
{{ message }}
Repository navigation
Commit 2bff2ea
Browse filesBrowse the repository at this point in the historyBrowse files
feat(browser): Report the INP target and interaction type as attributes (#24573)
The element and interaction type an INP was reported on only existed as
the span's name and op, which always have a value and so mislabel an INP
reported without an interaction as a click, fixed by reporting them as
`browser.web_vital.inp.target` and
`browser.web_vital.inp.interaction_type`, set only for what was actually
observed.
I added unit tests for an unresolved element and for an INP without an
entry, and the INP browser integration tests now expect both attributes.
Question for the review: should the "unknown" case be reported as
`<unknown>` or as `unknown` without the brackets, or omit it entirely? I
chose to omit it for now.
ref Conventions PR:
getsentry/sentry-conventions#641
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ Work in this release was contributed by @psh4607, @thijsw, @trinitiwowka, @nehap
9
9
- ref(browser)!: LCP and CLS spans no longer set `browser.web_vital.lcp.report_event` and `browser.web_vital.cls.report_event`. With per-navigation web vitals (the default) the attribute was already never set; it is now also gone when `softNavigations` and `bfcacheNavigations` are turned off. When the values are finalized is unchanged.
10
10
- feat(browser)!: `browser.navigation.type` on web vital and bfcache navigation spans now carries the navigation type exactly as web-vitals reports it. `bfcache` is now `back-forward-cache`, and a back/forward navigation that missed the bfcache (`back-forward`) or a discarded-tab restore (`restore`) is no longer folded into `navigate`. Update any dashboards or alerts filtering on `bfcache`.
11
11
- feat(browser): The pageload span now carries `browser.navigation.type`, the navigation type web-vitals reported TTFB and FCP for. Those vitals, and FP, are attributes of the pageload span rather than spans of their own, so until now there was no navigation type to read them against.
12
+
- feat(browser): INP spans now carry `browser.web_vital.inp.target`, the element the user interacted with, and `browser.web_vital.inp.interaction_type` (`click`, `hover`, `drag` or `press`). Both were only available as the span's name and op, which always have a value. The attributes are left out when there is nothing to describe: an INP that web-vitals reports without an interaction gets neither, and an element that could not be resolved gets no target.
12
13
- feat(core): Add `createFetchIntegration`, the shared implementation behind the global-`fetch` integrations in `@sentry/bun`, `@sentry/cloudflare`, `@sentry/deno` and `@sentry/vercel-edge`. Those four packages carried four copies of it; they now share one. Two changes come out of that:
13
14
- All four gain a `tracePropagation` option (default `true`). Turn it off to stop injecting `sentry-trace` and `baggage` without also turning off spans. To scope propagation to specific URLs, keep using `tracePropagationTargets` in the client options.
14
15
- Integration options now follow the client. Previously a second `Sentry.init()` in the same process silently reused the options of the first one.
0 commit comments