2023-07-11: Apdex SLO alert for sidekiq shard urgent_cpu_bound
Customer Impact
Brief delay in starting some sidekiq jobs.
Current Status
Some sidekiq jobs (mostly CI-related) classified under the urgent_cpu_bound
and urgent_other
shards experienced a longer startup delay than usual. This correlates with a transient spike in the response time of some external dependencies. The response time returned to normal within a few minutes, and the small backlog of jobs finished clearing a few minutes later.
📚 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 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.