Span descriptions/Transaction names unhelpful in javascript/cloudflare

[Dhrumil-Sentry]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/cloudflare

SDK Version

9.12.0

Framework Version

No response

Link to Sentry event

https://sentry.sentry.io/traces/trace/16cda0d729914c0795f6b02f13e13ee2/?environment=development&node=txn-b66497e9536a46a592e675f0b709171e&project=4509062593708032&source=traces&statsPeriod=14d&targetId=87ecc6bde99f790f&timestamp=1744221827

Reproduction Example/SDK Setup

Feedback from Cramer:

All the URLs being normalized in this manner makes this very unhelpful (Query)

It is also confusing to see the span details and see both url.full as an attribute and url as a tag - Are they supposed to be different?

Steps to Reproduce

.

Expected Result

Server calls would have meaningful names

Actual Result

.

[lforst]

We should also raise this with ingest. The SDK is sending the full url as description but relay replaces path segments with *. Maybe we shouldn't just straight up override that data but instead let releay add a separate attribute that contains a parameterized/grouped description.

[Dav1dde]

Looking through the data, while really aggressive and really bad for the UI, there was a huge burst in transaction names from requests to URLs which does not exist and end up in a 404, which explains why the transaction name clusterer generated these rules. Afaik the Django/Python SDK groups such requests into a single transaction (all requests that go to non-existent routes).

Is that not possible to do in the SDK here?

[lforst]

Yes we could do that but it's comes with nuance since it is strongly behavior altering.

[mydea]

Is there anything we want to do about this? I would also move this to ingest, as it is not really an SDK issue I believe…? Or not sure what the SDK should do differently here?