search

getsentry / sentry

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

Make CSP / NEL better in issue stream #68260

Open HazAT opened 4 months ago

HazAT commented 4 months ago

Problem Statement

I think we should capitalize on CSP and NEL way more - these are valuable and reliable source of problems in your app right now, the way we surface these in our product really isn't doing them justice - they just produce noise (by default, see our nextjs docs project https://sentry.sentry.io/issues/?project=1267915&referrer=sidebar&statsPeriod=24h)

We have also more than CSP, here is the post about NEL Nel: https://vanguard.getsentry.net/p/clt7n7u3e0000s60q3pdcz420

And maybe in the future, we also will have it for errors and other types: https://github.com/getsentry/relay/issues/3346

Solution Brainstorm

We could hide them by default (from the feed) - and try to correlate them to errors/transactions via the URL for example and group them a bit better / use different fields for the list view

Product Area

Issues

Related

https://github.com/getsentry/sentry/issues/60242

smeubank commented 1 month ago

these are valuable and reliable source of problems in your app

are there some examples? If I get CSP or NEL error X then I know I need to do Y

If these are turned on today, will this event type count agains the errors quota?

Client side sampling and filtering doesn't seem to be reliable, as SDK is not involved by default. We'd need server side filtering and sampling for these, IMO