# Order troubleshooting tests by likelihood and risk

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Order troubleshooting tests by likelihood and risk

ID: MHC-D-RESEARCH-0298 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/order-troubleshooting-tests-by-likelihood-and-risk

Do not reboot the world to answer a question a safe check could settle.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Several tests could be run next and some are disruptive, slow or expensive.

### Avoid when

- Likelihood estimates are judgment calls; do not let a familiar checklist override clear contrary evidence.

### Explanation

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.

### Example

Check whether the expected endpoint is reachable before enabling verbose production tracing that may worsen latency.

### Check

You can explain why the chosen test comes before the more invasive alternatives.

### Limits

- Likelihood estimates are judgment calls; do not let a familiar checklist override clear contrary evidence.

### Evidence and sources

- supports: Google SRE recommends considering obvious causes first and ordering tests with both likelihood and risk to the system in mind. — RS-A4A16C807A94C9D8. A low-risk common check should not become ritual if evidence already points strongly elsewhere. (Test and Treat; test design considerations)
- RS-A4A16C807A94C9D8: Effective Troubleshooting — https://sre.google/sre-book/effective-troubleshooting/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-a-hypothesis-test-result-ledger
