Consider removing client-side Sentry configuration
As discussed in https://gitlab.com/gl-retrospectives/sharding-group/-/issues/17#note_1014473784, during the CI decomposition cutover we found that when GitLab.com was put in maintenance mode client-side errors flooded our Sentry instance, preventing us from seeing whether any production errors might be show-stoppers.
https://dashboards.gitlab.net/d/bd2Kl9Imk/host-stats?orgId=1&var-env=ops&var-node=sentry-01-sv-ops.c.gitlab-ops.internal&from=1656657572743&to=1657022144491 shows the effect of what happened over the weekend. It seems handling client side errors may cause over 50% of the CPU load, not to mention consume lots of database space:
I don't think anyone really looks at these errors, so I wonder if we should just disable this to avoid future issues. I propose we drop sentry.clientside_dsn
from the config.
/cc: @ayufan, @DylanGriffith, @tkuah, @jarv