RCA (Root Cause Analysis)

Root cause analysis (RCA) is the process of investigating why a failure occurred by asking what led to it, and what led to that, until you reach causes you can change. It is commonly part of a postmortem.

Why it matters

Fixing only the visible symptom, for example restarting a crashed process, restores service but leaves the cause in place. RCA aims to find process, design or tooling gaps so the incident does not return. In complex systems there is rarely one cause, so many teams prefer the phrase "contributing factors".

Example

The "five whys" technique:

1. The site returned 503. Why? The app servers ran out of database connections.
2. Why? A new query held connections for several seconds.
3. Why? It lacked an index on a large table.
4. Why was it released? Query performance was not tested with production-sized data.
5. Why? There is no staging dataset of realistic size.

Actions: add the index, create a realistic staging dataset, alert on pool saturation.

Common mistakes

• Settling on "human error". Ask why the system allowed the error.
• Naming one cause when several factors combined.
• Skipping evidence and relying on assumptions. Check logs, deploy history and metrics.

Related

• Postmortem
• Blameless culture
• Incident
• टूल: Outage root cause finder

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.