Replace the old Sentry with the upgraded version
Let's follow https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/15372+ for CustomersDot and make sure we can use the new Sentry version.
It looks like we will be using Okta and some configuration may be needed on the Sentry side - to be confirmed by Infrastructure.
Other than that, we should upgrade the gem
and update the configuration to point to the new Sentry on CustomersDot
Rollout plan:
-
Add the new Sentry public DSN to our Ansible playbook: https://gitlab.com/gitlab-org/customersdot-ansible/-/merge_requests/399 -
Point Staging and Staging-Ref to the new Sentry instance: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/6768 -
Slack integration -
Review list of Sentry features used by the Fulfillment team before migrating Production -
Point Production to the new Sentry instance -
Create a new Slack alert (duplicate Staging one) immediately after Production switch over -
Update documentation accordingly -
Upgrade the Sentry gem (migration guide)
Edited by Etienne Baqué