2023-05-18: PVS Apdex violation

Customer Impact

Current Status

This incident was a RootCauseFalseAlarm and we think it's related to a know issue with how we are calculating the apdex in scalability#2319

1. The underlying metric seems fine 👉 #14454 (comment 1395928511)
2. Only 1 request that was above the SatisfactoryLatency 👉 #14454 (comment 1395914116)
3. This is a low RPS service 👉 #14454 (comment 1395926204)
4. Apdex dropped to 0% and then went above 1.0 👉 #14454 (comment 1395934596)

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