Resolve "Replace raven-js with @sentry/browser"
What does this MR do?
- Use @sentry/browser SDK instead of raven-js
- Update raven-js config/init to use Sentry
- Update webpack config to use new Sentry SDK
- Update raven-js specs for @sentry/browser
- Use new @sentry/browser methods
- Use latest @sentry/browser version
- Update SentryJS sample rate
- Update deprecated config values in SentryJS
- Set TODO to remove IGNORE_ERRORS from Sentry
- Update spec for BLACKLIST_URLS
- Rename/rework raven_js_spec to sentry_js_spec
- Move SAMPLE_RATE to const to fix spec
- Update and migrate Sentry specs to Jest
- Update sentry_js rspec
Testing instructions
- Get access to Sentry (ping me if you need it)
- Set up Sentry config values (example in gdk/config/gitlab.yml.example)
- Use DSN values from https://sentry.gitlab.net/settings/gitlab/fe-playground/keys/
- Trigger a JS error of choice in the GDK
- Observe error in Issues list (https://sentry.gitlab.net/gitlab/fe-playground/)
- ???
- Approve this MR!
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #26138 (closed)