Investigate Sentry profiling and performance features
We're currently only using Sentry for exceptions tracking, but they also offer performance and now profiling-related features. See https://sentry.io/for/performance/ and https://blog.sentry.io/2022/11/21/profiling-for-python/#working-with-date-times
┆Issue is synchronized with this Jira Task
We've enabled it on dev only for now and found ~~a couple~~ one interesting thing right out of the box that we fixed (the second thing is a red-herring):
- https://github.com/mozilla/addons/issues/9003
- ~~https://github.com/mozilla/addons/issues/1837~~
We should use before_send_transaction from sentry_sdk 1.14.0 to also strip sensitive data from performance profiles.
Temporarily disabled on dev through the SENTRY_TRACES_SAMPLE_RATE env variable (set to 0) while we investigate other issues
According to an email I got from Sentry, profiling is going to be out of beta on 1st May. (And transactions with profiling enabled will be "charged" at 1.3x the rate of transactions without profiling - though I don't have any insight into our plan/budgets/billing to know if this would be a concern)
Old Jira Ticket: https://mozilla-hub.atlassian.net/browse/ADDSRV-134