Effective Troubleshooting¶
Jones, C. (2016). Effective Troubleshooting. Site Reliability Engineering: How Google Runs Production Systems.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Troubleshooting Flowchart
- Ordered to eliminate fastest — good charts front-load the checks that rule out the most (or the most likely) causes, reaching the fault in the fewest steps.
This sourceRecommends ruling hypotheses in or out with discriminating tests, checking likely causes first, and using bisection to reduce the search space.
- Ordered to eliminate fastest — good charts front-load the checks that rule out the most (or the most likely) causes, reaching the fault in the fewest steps.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:6bc03947578f · see in the full table