2022-11-18: The goserver SLI of the gitaly service on node `file-65-stor-gprd.c.gitlab-production.internal` has an error rate violating SLO
Current Status
Gitaly saturation on a specific node, caused by a specific user or two. I expect this incident alert to resolve on its own.
This incident was caused by a known saturation culprit for which silences have been created previously during the week, and to whom contact efforts have already been made by support staff.
See internal comment for culprit identification: #8071 (comment 1177936349)
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 References and helpful links
Recent Events (available internally only):
- Deployments ❙ Feature Flag Changes ❙ Gitlab.com Latest Updates ❙ Runbook for Release Rollback
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.