Skip to content

Instantly share code, notes, and snippets.

@MatthewRDodds

MatthewRDodds/troubleshooting_methodology.md

Created April 25, 2017 02:45
Show Gist options
  • Save MatthewRDodds/d2d7abadcbd6b58a5680acac3f7744ac to your computer and use it in GitHub Desktop.
Save MatthewRDodds/d2d7abadcbd6b58a5680acac3f7744ac to your computer and use it in GitHub Desktop.
Download ZIP
Troubleshooting methodology
Raw
troubleshooting_methodology.md

Troubleshooting Methodology

Source

Investigation

  • Problem Statement: Create a clear, concise statement of the problem.
  • Problem Description: Identify the symptoms. What works? What doesn't?
  • Identify Differences and Changes: What has changed recently? What is unique about this system?

Analysis

  • Brainstorm: Gather Hypotheses: What might have caused the problem?
  • Identify Likely Causes: Which hypotheses are most likely?
  • Test Possible Causes: Schedule the testing for the most likely hypotheses. Perform any non-disruptive testing immediately.

Implementation

  • Implement the Fix: Complete the repair.
  • Verify the Fix: Is the problem really fixed?
  • Document the Resolution: What did we do? Get a sign-off from the system owner.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment