Raw URLs sent as Transaction

[smeubank]

Environment

How do you use Sentry?
Sentry SaaS (sentry.io)

Which SDK and version?
sentry-laravel 2.12.0

Steps to Reproduce

Sending transactions

Expected Result

High quality transactions

Actual Result

for sentry laravel (2.12.0) we're getting raw URLs and bad transactions. we noticed:

• OPTIONS has raw URLs. probably shouldn't be recorded to begin with
• there's a bunch of transactions reported without http.method
• 404s are missing the http.status, and those also come with raw URLs

[smeubank]

for more context, to improve the performance product experience, we are working to improve transaction naming

meaning that in product we don't have a ton of unique transactions because of poor parameterization from different platforms

Meaning the org slug …/sentry/… becomes …/:orgId/…

1. all web SDKs should now send source: dev spec
2. DSC spec regarding transaction name quality

[smeubank]

and sentry-symphony sends URLs for everything

[smeubank]

@jan-auer is there some data we can share with @stayallive regarding

there's a bunch of transactions reported without http.method

for option we we agreed to exclude similar to other SDKs it is not useful

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[cleptric]

@stayallive We should take this into consideration for the DS rollout.

[stayallive]

So to summarize, we should exclude the following transactions by default:

• 404's (hard 404's for missing routes)
• OPTIONS requests (mostly because of CORS)

For the 404's there are 2 types, the ones where there is no matching route (which defaults to a 404) or where there is a route but the developer throws a 404 because of a incorrect ID or some other reason. I assume we only want to exclude the first type not the second?

In addition to that, do we allow developers to override this behaviour in some way if they do want to see OPTIONS in their transactions for some reason?

[cleptric]

The biggest "issue" right now are the hard 404's for missing routes.
This creates alerts in the product, with no way for the user to fix it.

In regards to OPTIONS requests, there are currently some discussions from SDK folks going on internally, so we can wait and leave these transactions as is for the time being.