Heuristic
Order troubleshooting tests by likelihood and risk
Do not reboot the world to answer a question a safe check could settle.
Before you use it
- Use when
- Several tests could be run next and some are disruptive, slow or expensive.
Keep this limit in mind
- Likelihood estimates are judgment calls; do not let a familiar checklist override clear contrary evidence.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
For each plausible next test, consider how likely its target explanation is, what the test can distinguish, and what harm or state change the test can cause. Run cheap, low-risk, high-plausibility checks first unless stronger evidence justifies a different order. The sequence itself is part of incident safety.
An example
Check whether the expected endpoint is reachable before enabling verbose production tracing that may worsen latency.
Check your result
You can explain why the chosen test comes before the more invasive alternatives.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingOrder troubleshooting tests by likelihood and risk
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaPrefer a test that kills hypotheses
Evidence and sources
Google SRE recommends considering obvious causes first and ordering tests with both likelihood and risk to the system in mind.
A low-risk common check should not become ritual if evidence already points strongly elsewhere.
Effective Troubleshooting · Test and Treat; test design considerations
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.