Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discover - Make Query string parameters searchable for CSP errors #78674

Open
Angelodaniel opened this issue Oct 7, 2024 · 3 comments
Open
Labels
Migrated Product Area: Discover Sync: Jira Apply to auto-create a Jira shadow ticket

Comments

@Angelodaniel
Copy link
Member

Angelodaniel commented Oct 7, 2024

Problem Statement

Currently CSP errors cannot be altered on the SDK side as there is not really an SDK that is in between there so they are all captured automatically (#73817)

CSP errors do capture a lot of metadata that the Developers can use to get alerted or split out the noise.
The problem is that in this case metadata like the Query String is not queryable throughout the platform
Image

Solution Brainstorm

Make more data available for search/alert/query functionality from CSP errors in specific

Product Area

Unknown

┆Issue is synchronized with this Jira Improvement by Unito

@Angelodaniel Angelodaniel added the Sync: Jira Apply to auto-create a Jira shadow ticket label Oct 7, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Oct 7, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Oct 8, 2024

Routing to @getsentry/product-owners-discover for triage ⏲️

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 3 Oct 8, 2024
@Dhrumil-Sentry
Copy link

Thanks for this feedback, it's a valid ask and we will add it to our backlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Migrated Product Area: Discover Sync: Jira Apply to auto-create a Jira shadow ticket
Projects
Status: No status
Development

No branches or pull requests

3 participants