feat(attributes): Add browser.navigation.type, move navigation.* to router.navigation.* - #600
Merged
Merged
Conversation
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Attributes
Names
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
logaretm
force-pushed
the
awad/browser-navigation-type
branch
from
August 28, 2026 14:46
599d4ed to
922a1fd
Compare
logaretm
marked this pull request as ready for review
August 28, 2026 14:46
logaretm
requested review from
a team,
Lms24,
cleptric,
mjq and
nsdeschenes
as code owners
August 28, 2026 14:46
logaretm
changed the title
logaretm
added a commit
to getsentry/sentry-javascript
that referenced
this pull request
Aug 28, 2026
…red on Adds `browser.navigation.type` to every emitted LCP, CLS and INP span, so a vital can be read against the kind of navigation that produced it. A soft navigation and a cold page load are not comparable measurements, and without this there is no way to separate them after the fact. web-vitals reports a wider set of navigation types than the attribute defines, so only the states Navigation Timing cannot express keep their own value. Every ordinary document navigation folds into `navigate`, including a back/forward that missed the bfcache (per the spec) and a `document.wasDiscarded` restore, which the spec does not name at all. The `back-forward-cache` -> `bfcache` mapping is included but unreachable today: `withoutBfcache` drops those metrics before they reach a span. It's here so that enabling bfcache vitals later doesn't silently report them as `navigate`. Spec: getsentry/sentry-conventions#600
logaretm
added a commit
to getsentry/sentry-javascript
that referenced
this pull request
Aug 31, 2026
…red on Adds `browser.navigation.type` to every emitted LCP, CLS and INP span, so a vital can be read against the kind of navigation that produced it. A soft navigation and a cold page load are not comparable measurements, and without this there is no way to separate them after the fact. web-vitals reports a wider set of navigation types than the attribute defines, so only the states Navigation Timing cannot express keep their own value. Every ordinary document navigation folds into `navigate`, including a back/forward that missed the bfcache (per the spec) and a `document.wasDiscarded` restore, which the spec does not name at all. The `back-forward-cache` -> `bfcache` mapping is included but unreachable today: `withoutBfcache` drops those metrics before they reach a span. It's here so that enabling bfcache vitals later doesn't silently report them as `navigate`. Spec: getsentry/sentry-conventions#600
…to `router.navigation.*` Adds `browser.navigation.type` for the browser-level navigation type reported by the web-vitals library, and moves the client-side router navigation attributes into the `router.*` namespace: - `navigation.type` -> `router.navigation.type` - `navigation.origin` -> `router.navigation.origin` - `navigation.route.id` -> `router.navigation.route.id` The old `navigation.*` attributes are deprecated with backfill, and the `sentry.sveltekit.navigation.*` deprecations are re-pointed at the new `router.*` replacements.
Lms24
force-pushed
the
awad/browser-navigation-type
branch
from
September 2, 2026 10:56
3ad42dc to
5121053
Compare
Lms24
enabled auto-merge (squash)
September 2, 2026 10:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds
browser.navigation.typefor web vital spans:navigate,reload,prerender,bfcache,soft-navigation. Mirrors what the web-vitals library reports asnavigationType.Also moves the
navigation.*attributes torouter.navigation.*so the router's own navigation type stops competing with the browser's.navigation.type,navigation.originandnavigation.route.idare deprecated with plain backfills, and the sveltekit aliases now point at the new names. These are straight renames so there's no transform involved.The new attribute is going to be used to distinguish the various web vital signals so users can filter out specific (faster) types of navigations.