We (probably) don't need Sentry to run on the Django Admin pages. We're getting a lot of errors around the use of jQuery and inline styles that would be a disproportionate amount of work to fix. This will also make managing "real" errors easier to discover and manage in Sentry.
Changes proposed in this pull request
Filter out all admin pages
Notes
This hasn't been properly tested yet - we can monitor this once deployed
Does this sound like a sensible thing to do?
Does the code look sensible?
Things to check
[ ] I have added any new ENV vars in all deployed environments
Context
We (probably) don't need Sentry to run on the Django Admin pages. We're getting a lot of errors around the use of jQuery and inline styles that would be a disproportionate amount of work to fix. This will also make managing "real" errors easier to discover and manage in Sentry.
Changes proposed in this pull request
Notes
Things to check