Document Sentry policy for frontend developers
We integrate with Sentry to log production errors and we currently are not utilizing this as effectively as we should be. We should be checking and resolving open reports at sentry.gitlab.net/gitlab/gitlabcom-clientside, making sure that we eliminate noise, and file issues for bugs and regressions discovered here.
We should:
- Update our documentation to define a policy for working with Sentry.
- Update our on-boarding guides to suggest frontend developers familiarize themselves with Sentry and add the
#sentry-frontend
Slack channel to the list of suggested channels. - Document how we have been updating the Raven client and Sentry configuration to filter out noise from client-side content blockers, browser extensions, etc and ensure that we keep up on it so that our Sentry dashboard remains useful.