2024-10-22: The sidekiq_queueing SLI of the sidekiq service on shard low-urgency-cpu-bound has an apdex violating SLO

Customer Impact

Right now, the only real measurable customer impact we saw in the metrics may have been slowness in picking up jobs from pending to running. We are not aware of any customer tickets about this.

Current Status

Right now, it appears that the incident was related to a feature flag.

📝 Summary for CMOC notice / Exec summary:

1. Customer Impact: Possibly slow IC job pickup in runners.
2. Service Impact: ServiceSidekiq
3. Impact Duration: 21:58 - 22:44 ( 46 )
4. Root cause: TBD

📚 References and helpful links

Recent Events (available internally only):

• Feature Flag Log - Chatops to toggle Feature Flags Documentation
• Infrastructure Configurations
• GCP Events (e.g. host failure)

Deployment Guidance

• Deployments Log | Gitlab.com Latest Updates
• Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook

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 our 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.

Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.