2023-05-24: Code suggestions response time is > 240 seconds for the last hour+
Customer Impact
Load on code suggestions went up >3X with the in product messaging to encourage more use it). We have turned off the in-product messaging in the interim while we work the incident due to performance going from ~1 second to 240 ~seconds.
Current Status
We are continuing to see increased latency and unavailability on the code suggestions service. This corresponds to increase usage.
This is similar to the incident earlier today 2023-05-24: Code Suggestions Latency (#14516 - closed)
Usage
Latency
📚 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.