This rollout is enabled by having two sets of Sentry settings in our gitlab instance at once, the GitLab instance config (from gitlab.yml) and the settings (the UI). A rollout could consist of:
Ensure the Sentry config (e.g. in gitabl.yml) is present for the old Sentry instance (v9).
Enable configure_sentry_in_application_settings the enable Admin UI Sentry settings.
Visit /admin/application_settings/metrics_and_profiling to configure the Sentry settings for the new Sentry instance.
Progressive rollout of enable_new_sentry_clientside_integration to users. Users with the feature flag enabled will begin reporting to the new instance.
The recommended rollout method is percentage: 5%, 10%, ...
Once the rollout is complete, remove the dangling dependencies and remove this feature flag.
Screenshots or screen recordings
Errors appear to be reported the new Sentry instance:
How to set up and validate locally
Check out this branch and install run yarn.
This MR installs two versions of the Sentry Browser GDK, so we should test two integrations:
Legacy Integration
Ensure the feature flag for the new integration is disabled Feature.disable(:enable_new_sentry_clientside_integration)
Add Sentry (v9) DSN in gitlab.yml:
## Error Reporting and Logging with Sentry sentry: enabled: true dsn: https://XXXX@sentry.gitlab.net/1 clientside_dsn: https://XXXX@sentry.gitlab.net/1 environment: 'development'
Confirm events are captured by the old Sentry instance
New integration
Enable the feature flags to enable the new integration and the UI settings panel:
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
