2024-10-17: Large increase in graphql requests from ci_graphql_pipeline_mini_graph

Customer Impact

No Customer Impact.

Current Status

After disabling the feature flag

We are still seeing around 500 RPS from that endpoint, we believe this due to existing open MR pages which haven't been refreshed for a while causing the endpoint to be still hit.

We will keep the issue IncidentMitigated for now and IncidentResolved once this hits to 0.

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

Edited Oct 21, 2024 by Tarun Khandelwal
Assignee Loading
Time tracking Loading