2020-06-29: Customers app out of disk space

/label incident IncidentActive

Summary

Customers app out of disk space

The customers application is alerting that it is showing 500 errors. The / partition is out of disk space.

Timeline

All times UTC.

2020-06-29

  • 00:28 - dsylva declares incident in Slack using /incident declare command.
  • 00:38 - deleted a bunch of invalid log files from /home/gitlab-customers/customers-gitlab-com/log
  • 00:41 - gzipped large sidekiq log - site functionality restored
  • 00:48 - removed copy of log directory from last November that was taking up 3G of space

Click to expand or collapse the Incident Review section.

Incident Review

Summary

  1. Service(s) affected:
  2. Team attribution:
  3. Minutes downtime or degradation:

Metrics

Customer Impact

  1. Who was impacted by this incident? (i.e. external customers, internal customers)
  2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
  3. How many customers were affected?
  4. If a precise customer impact number is unknown, what is the estimated potential impact?

Incident Response Analysis

  1. How was the event detected?
  2. How could detection time be improved?
  3. How did we reach the point where we knew how to mitigate the impact?
  4. How could time to mitigation be improved?

Post Incident Analysis

  1. How was the root cause diagnosed?
  2. How could time to diagnosis be improved?
  3. Do we have an existing backlog item that would've prevented or greatly reduced the impact of this incident?
  4. Was this incident triggered by a change (deployment of code or change to infrastructure. If yes, have you linked the issue which represents the change?)?

5 Whys

Lessons Learned

Corrective Actions

Guidelines

  • Blameless RCA Guideline
Edited Jun 30, 2020 by Brent Newton
Assignee Loading
Time tracking Loading