liveBook · Manning

Root cause

A root cause is an underlying condition or factor that produces or substantially contributes to an observed problem, failure, or outcome.

How 5 Manning books explain it

The Art of Code

A root cause is the underlying condition or defect that initiates or substantially contributes to an observed failure.

How it is used
Uses root-cause investigation to move from reported failures to evidence-based solutions.
How deep it goes
Develops a four-stage procedure with hot and cold exploration, hypothesis evaluation, and fix validation.
Examples
Traces a failed web form through network and backend logs and investigates intermittent Java crashes with a heap dump.
What you can do after
Diagnose failures by tracing evidence, testing possible causes, and validating fixes for side effects.

Read how The Art of Code explains root cause →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

The underlying condition or defect that produces an observed software problem.

How it is used
Guides investigation and repair of problems in distributed microservices.
How deep it goes
Outlines investigation through hypotheses and experiments, followed by fixing, test-based verification, and reflection.
Examples
Uses a failing automated test that reproduces a problem as a yardstick for a fix.
What you can do after
Diagnose and debug by narrowing possible causes, testing hypotheses, and checking a fix against a reproducing test.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains root cause →

Think Like a Software Engineering Manager

A root cause is an underlying factor responsible for an observed outcome, problem, or change.

How it is used
Uses root-cause analysis to respond to morale problems, employee departures, and opportunities for process improvement.
How deep it goes
Defines the idea and gives diagnostic categories and responses, but stops short of a formal analytical method or causal model.
Examples
Uses stressed employees, David’s resignation, family relocation, project dissatisfaction, and postdeparture feedback as practical examples.
What you can do after
Diagnose whether a problem is controllable, select a cause-matched response, and turn departures into retention or process improvements.

Read how Think Like a Software Engineering Manager explains root cause →

Troubleshooting Java, Second Edition

The underlying reason a software behavior or failure occurs.

How it is used
Guides investigation from an observable failure toward the earlier condition that produced it.
How deep it goes
Distinguishes symptoms from causes and outlines a multi-tool investigation, but does not provide a complete diagnostic procedure.
Examples
Uses NullPointerException stack traces and deadlock thread dumps as diagnostic examples.
What you can do after
Diagnose/debug with it by tracing failures beyond their visible exceptions and selecting further investigation techniques.

Read how Troubleshooting Java, Second Edition explains root cause →

Writing for Developers: Blogs that get read

The underlying defect or condition that produces an observed software failure.

How it is used
Guides bug hunts from observed symptoms toward the specific defect or condition producing them.
How deep it goes
Traces failures through investigation steps and analysis tools, stopping at identifying the responsible mechanism rather than prescribing universal fixes.
Examples
Uses ZFS CPU analysis, Java memory leaks, garbage collection, and Zig translation problems involving legacy C macros.
What you can do after
Diagnose/debug with analysis and observability tools by narrowing symptoms to a responsible function, mechanism, or defect.

Read how Writing for Developers: Blogs that get read explains root cause →

Also covered in

What to know first

Related concepts

Questions about root cause

What is root cause?

A root cause is an underlying condition or factor that produces or substantially contributes to an observed problem, failure, or outcome.

Which Manning books explain root cause?

The Art of Code, Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform, Think Like a Software Engineering Manager, Troubleshooting Java, Second Edition and Writing for Developers: Blogs that get read.

What should I know before learning root cause?

Manning books that teach root cause usually introduce Java, pipeline, workflow and cascading failure first.

What is the difference between root cause and exception?

A root cause is an underlying condition or factor that produces or substantially contributes to an observed problem, failure, or outcome. An exception is a runtime signal or value representing an abnormal condition that interrupts ordinary program flow and can be handled or propagated.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.