Repository navigation
Ember pageload and navigation spans lack span description inference attributes #24284
Description
Description
Surfaced via #24168 (comment), Ember pageload (and likely also navigation) spans don't carry a name that's equal to any of the attributes we need to infer the span description: https://getsentry.github.io/sentry-conventions/descriptions/#browser-pageload
We have a couple of options:
router.navigation.route.id- theoretically,
url.templatebut the current pattern in the test doesn't seem to actually be a url - we override this with
sentry.descriptionto avoid span description inference and define the description locally in the SDK.
Metadata
Metadata
Assignees
Projects
- Status
Activity
linear-code commentedon Sep 10, 2026
JS-3649
ihsraham commentedon Sep 13, 2026
I'm interested in a small fix here. The current browser conventions prioritize
router.navigation.route.id, while the Ember integration already has the route name. Would adding that attribute for pageload/navigation, with regression coverage through the streamed Ember app, fit the intended direction? I'd preserve the existing names and fallback behavior. I haven't run the reproduction yet. Is anyone already covering this, and should the attribute hold the raw route name or the existingroute:form?msonnb commentedon Sep 14, 2026
Hi @ihsraham! Thanks for offering your help, I think that fits the intended direction, yes! I'd include the existing
route:prefix since that matches the currentname.fix(ember): Add route IDs to pageload and navigation spans (#24372)
github-actions commentedon Sep 23, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #24372, which was included in the 11.0.0 release.