search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.09k stars 4.2k forks source link

Origin as built-in tag for Content Security Policy violation reports #73818

Open mortargrind opened 4 months ago

mortargrind commented 4 months ago

Problem Statement

For CSP violation reports, we should have origin as a built-in tag.

Use-case: currently trying to have a widget that can show us the CSP violations per origin because the app in question follows a country based deployment via separate subdomains (de.app.com, uk.app.com). Instead I am only able to see a very fragmented list based on URLs de.app.com/login , de.app.com/home etc.).

Custom tags are also can be used to achieve this (if they are supported) but considering we already have the document URI, the info is already there and better to be supported as a built-in tag.

Solution Brainstorm

No response

Product Area

Issues

┆Issue is synchronized with this Jira Improvement by Unito

getsantry[bot] commented 4 months ago

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

snigdhas commented 4 months ago

Adding this to our backlog to consider for Q4