Sentry reports around 2K errors per day in `/api/graphql`
Summary
Sentry's frontend project (gitlabcom-clientside
) is reporting a large number of errors since May 25, 2021 2:56:33 PM UTC
Sentry links (internal):
- (old) https://sentry.gitlab.net/gitlab/gitlabcom-clientside/issues/2657256/
- (old) https://sentry.gitlab.net/gitlab/gitlabcom-clientside/issues/2720743/
All these errors are NetworkError
, so are akin to 500 errors where the failure is on GitLab side. Also, although sentry reports this start one month ago, Sentry may have been disabled at some point.
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
No single group or component appears to be affected:
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Edited by Mark Florian