Reading: Post-Mortem: Incident #4092
Lectură: Jurnalul detaliat al unui incident. Citește cronologia unui post-mortem real pentru a înțelege cum s-au desfășurat evenimentele pas cu pas în timpul unei crize.
Чтение: Подробный журнал инцидента. Прочитайте хронологию реального разбора полетов, чтобы понять, как события развивались шаг за шагом во время кризиса.
Post-Mortem: Incident #4092
Olivia: 23:42 — Monitoring tool detects a sudden surge in slow queries on the primary database in Denver.
Sean: 23:45 — The primary database runs out of disk space and stops responding entirely.
Lauren: 23:47 — Automated failover initiates, but a severe deadlock prevents the replica from promoting.
Olivia: 23:50 — First critical alert is sent via email to Alex Miller, who had left the company in 2019.
Sean: 23:55 — On-call engineers finally notice the Slack escalation and open the war room.
Lauren: 00:15 — Team checks data integrity and confirms severe table corruption.
Olivia: 01:30 — After a sleepless night of running recovery scripts, the system is brought back online.
Read again and choose the right answer
What happened at 23:45 according to Sean?
- The primary database ran out of disk space
- The team went home
- The greenfield project launched
Why did the automated failover fail at 23:47?
- Because of a power outage
- Because a severe deadlock prevented replica promotion
- Because nobody was online
What unexpected detail was discovered at 23:50?
- The alert went to an engineer who left in 2019
- The server was unplugged
- The wiki was deleted
When was the system finally brought back online?
- At 23:42
- At 00:15
- At 01:30
Sources: photo by Vito Goričan on Pexels
Despre această lecție
Această lecție se concentrează pe povestirea incidentelor tehnice folosind timpurile trecute în engleză. Vei exersa narațiuni complexe legate de căderi de baze de date.
Об этом уроке
Этот урок посвящен описанию технических инцидентов с использованием прошедших времен в английском языке. Вы отработаете сложные рассказы о сбоях баз данных.