Troubleshooting Methodology
A disciplined workflow prevents random troubleshooting and unnecessary production impact.
Core investigation flow
Client report
→Define symptom
→Server health
→Processes
→Services
→Logs
→Application / IIS
→Plesk / Config
→Root cause
→Fix
→Verify
→Document
→Golden rules
Do not guess.
Do not reboot blindly.
Do not kill unknown processes blindly.
Do not delete files blindly.
Collect evidence first.
Change one thing at a time.
Verify after change.
Document what you found.
Ask the class
Customer says: “The server is slow.” What is your first move?
Define the symptom and check server health: CPU, RAM, disk and network. Then move into processes, services and logs.