Skip to content

Unparametrized Paths Not as Useful #15411

Closed
Closed
@smeubank

Description

@smeubank

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

9.x.x

Framework Version

sentry docs

Link to Sentry event

https://sentry.sentry.io/issues/6267953287/?project=1267915&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&sort=date&statsPeriod=14d&stream_index=0

Reproduction Example/SDK Setup

There's 2 scenarios to address, potentially this should be 2 different issues:

  1. often see issues in sentry for Next.js (maybe others too) that have "incomplete-app-router-transaction"
  2. often see issues where the route is partially not fully paramterized

Both of these can have a negative impact on grouping, creating more noise.

Steps to Reproduce

Image

the 2nd we don't have great examples in the docs project, but we can easily see it quite often in many setups.

Expected Result

Parameterized routes, and none of this "incomplete-app-router-transaction" business

Beautifully grouped issues == less noise

Actual Result

not

Metadata

Metadata

Assignees

Labels

Package: nextjsIssues related to the Sentry Nextjs SDK

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions