Overview
This lesson covers the "follow the cookie crumbs" troubleshooting method, which involves tracing problems back to their origin point and working forward. The approach emphasizes asking when problems started and using system logs to identify root causes rather than addressing symptoms.
Follow the Cookie Crumbs Method
- Core principle: identify when the problem first occurred and work forward from that point
- Key diagnostic question: "When did this problem start?"
- Ask users what changed between when the system worked and when it failed
- This historical approach reveals context that simple symptom descriptions miss
- Changes like updates, installations, or configuration modifications often trigger issues
Troubleshooting Approach Comparison
| Approach | Method | Result |
|---|
| Symptom-focused | Reinstalling the crashing app immediately | Failed to resolve issue |
| Timeline-based | Asked when problem started; discovered recent update | Identified bug in update; rolled back version successfully |
Using System Logs
- Logs function as the system's diary, recording dates and events chronologically
- Review logs at the exact time a failure occurred to find defining events
- Logs reveal patterns and changes that users may not remember or notice
- Cross-reference user reports with log data for complete troubleshooting context
Working with Error Messages
- Error messages are helpful indicators pointing toward the root cause
- Single errors can trigger cascades of subsequent errors throughout the system
- Always start troubleshooting from the first error, not the most recent
- Fixing the root error typically resolves all downstream errors automatically
- Some errors are self-explanatory: 404 not found for moved/deleted pages, permission denied for protected files
- Avoid spending time on cascading errors when the root cause is higher in the log