07/07/2026
๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐ถ๐ผ๐ป ๐ ๐ฎ๐ฟ๐ธ๐ฎ ๐๐ ๐๐ต๐ฎ๐ฐ๐ผ: ๐ ๐ฎ ๐ง๐ฎ๐ต๐ฎ๐ ๐๐ฎ๐ฏ-๐ฑ๐ฒ๐บ๐ถ๐๐ฒ, ๐๐ถ๐ถ๐๐ฎ๐ฎ๐ป๐ด๐ฒ๐น๐ถ๐๐ฒ, ๐บ๐ถ๐๐ฒ ๐ซ๐ฎ๐น-๐ฟ๐ฎ๐ฎ๐ฑ๐ถ๐๐ฒ?
Waa Qamiis, 4:58 ๐ด๐ฎ๐น๐ฎ๐ฏ๐ป๐ถ๐บ๐ผ.
Monitoring-kii ayaa qaylo bilaabay. Production-kii wuu dhacay.
Saddex engineer ayaa ka jawaabay hal incident, laakiin mid walba wuxuu muujiyay dhaqan ka duwan.
๐ฅ Dab-demiye
Server-ka ayuu galay, service-kii ayuu restart gareeyay, traffic-kiina wuu soo noqday.
โWaan hagaajiyay,โ ayuu yiri.
Laakiin ticket ma jiro. Root cause ma jiro. Documentation ma jiro.
Bisha xigta, isla incident-kii ayaa soo noqday.
๐ Diiwaangeliye
Post-mortem dheer ayuu qoray: timeline, analysis, contributing factors, iyo action items badan.
Laakiin qofna si dhab ah uma akhrin. Action items-kiina lama fulin.
Bisha xigta, isla incident-kii ayaa soo noqday.
๐ง Xal-raadiye
Isagu ma weydiiyo:
โYaa qaladka sameeyay?โ
Wuxuu weydiiyaa:
โMaxaa system-keennu u oggolaaday in qaladkani dhaco?โ
Farqigaas ayaa muhiim ah.
Blameless post-mortem micnihiisu ma aha in accountability la iska dhaafo. Micnihiisu waa in aan diiradda saarno system-ka, process-ka, monitoring-ka, checklist-yada, iyo guardrails-ka naga maqan.
Action item dhab ah ma aha:
โImprove monitoring.โ
Action item dhab ah waa:
โKu dar alert database connection pool exhaustion ah marka threshold-ku gaaro 80%, owner leh, deadline leh.โ
5 Whys waxay kaa caawisaa inaad ka gudubto jawaabta fudud:
โDeveloper-ka ayaa ilaaway.โ
Oo aad gaarto jawaabta system-ka ah:
โMa lihin waardiye ka hortaga in la ilaawo.โ
Teams-ka reactive-ka ah waxay hagaajiyaan symptom-ka.
Teams-ka resilient-ka ah waxay hagaajiyaan system-kii symptom-ka keenay.
Marka xigta ee monitoring-ku qaylo bilaabo, is weydii:
Ma waxaan nahay ๐๐ฎ๐ฏ-๐ฑ๐ฒ๐บ๐ถ๐๐ฒ๐๐ฎ๐ฎ๐น, ๐๐ถ๐ถ๐๐ฎ๐ฎ๐ป๐ด๐ฒ๐น๐ถ๐๐ฒ๐๐ฎ๐ฎ๐น, ๐บ๐ถ๐๐ฒ ๐ซ๐ฎ๐น-๐ฟ๐ฎ๐ฎ๐ฑ๐ถ๐๐ฒ๐๐ฎ๐ฎ๐น?
