2023-10-08: The Disk Utilization Overall resource of the logging service (main stage) has a saturation exceeding SLO and is close to its capacity limit
Customer Impact
No customer impact.
Current Status
Exporters have detected that some deployment indices have nudged the gitlab-logs-prod
ELK deployment disk capacity over its 90% threshold.
The further back I look at these metrics, the less I like the current situation.
Source: thanos
Past incidents indicate this could resolve on its own once index lifecycle management policies are triggered provider-side (elastic.co).
We currently look like this over the past week:
Source: thanos
The elastic.co deployment are all reporting as healthy.
Which is amusing, since all but one instance in us-central1-a
zone of the gitlab-logs-prod
deployment is reporting disk allocation at over 87%.
Source: elastic.co
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 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.