Context transaction name is not parametrized anymore

[HatemGr]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

I am using Sentry on a Next app.
At the same time I have upgraded:

• Sentry from ^9.19.0 to ^10.36.0
• Next from 15.5.10 to 16.1.6

I use the {{ transaction }} in my issues fingerprints for grouping.
When performing an API call, when error was throw I had in my fingerprint the parametried path (ex: api/employee/[id]. However, for the last week none of my issues are grouped because the fingerprint contains the actual variable values (ex: api/employee/1a2b3c-xyz)

This issue seem not to happen on all my Sentry issues :/

Has any change in Sentry been done that could trigger this change ?

Expected Result

Actual Result

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[linear]

ENG-6524

JS-1705

JS-1706

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[lobsterkatie]

This parameterization happens in the SDK, before the data gets to our servers, so I'm going to transfer this to the SDK repo.

[chargome]

Hey @HatemGr, could paste a link to one of these events? This would be a good place to start for us!