Ignore Network errors reporting to Sentry
What does this MR do and why?
Network errors create noise in Sentry and can't be debugged or fixed in the GitLab's software.
We can ignore them so our observability can be focused on issues we can fix.
References
- Original issue #503490
We get several thousand errors per day (project names are redacted):
- https://new-sentry.gitlab.net/organizations/gitlab/issues/?project=4&query=Network+Error&referrer=issue-list&sort=freq&statsPeriod=24h
- https://new-sentry.gitlab.net/organizations/gitlab/issues/?project=4&query=NetworkError&referrer=issue-list&sort=freq&statsPeriod=24h
Many errors reported by the runner alert at https://new-sentry.gitlab.net/organizations/gitlab/alerts/rules/gitlabcom-clientside/2/details/ should be ignored globally for the entire clientside project.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
NA
How to set up and validate locally
NA
Related to #503490
Edited by Miguel Rincon