Debug a System You Do Not Own: Logs, Access and Safe Changes
Follow one fault in a customer's environment from the complaint to the hand-back. Ask for the least access that will do, find the pattern in the logs, follow one message across two systems, reproduce the fault away from the live system, make the smallest change behind a switch, and prove it worked. All the code runs on your own machine with no account or key.
6 lessons 49 minNo account needed
Start lesson 1What you will learn
- Turn a customer's complaint into a precise symptom, and ask for the least access that will let you investigate it.
- Summarise a log before reading it, and set aside a loud error that is not the cause.
- Follow one message through two systems whose logs use different formats and different clocks.
- Reproduce a fault with a stand-in for the system you do not own, as a failing test.
- Make the smallest change on your own side, behind a switch, with a dry run and a way back.
- Prove from the logs that the change worked, and hand back what is not yours to fix.
Before you start
- Read and write basic Python: functions, loops, dictionaries, classes and imports.
- Run Python scripts from a terminal or command prompt.
- Python 3.9 or later installed. The course uses only the standard library, so nothing else is needed.
Lessons
- Lesson 1: Before You Touch Anything: Who Owns What and What You May DoMeet the case that runs through the course, draw the line between the code you own and the systems you do not, ask for the least access that will do, and turn a complaint into a symptom you can test.7 min
- Lesson 2: Read the Logs: Find the Pattern Before the CauseGet one day's logs, summarise them before reading a single line, set aside the loudest error with a reason, and write down the pattern the real problem follows.8 min
- Lesson 3: Follow One Message Across Two SystemsLine up two logs that use different formats and different clocks, follow one reminder from the service to the gateway and back, and measure how large the fault is.9 min
- Lesson 4: Reproduce It Safely, Away from the Live SystemRead the code you own, build a small stand-in for the system you do not own, and capture the fault as a failing test that sends nothing to anybody.7 min
- Lesson 5: Make the Smallest Safe ChangeWeigh the possible fixes by who owns them and what they hide, make the smallest change on your own side behind a switch, try it without sending anything, and write the plan the customer approves.9 min
- Lesson 6: Check It Worked, Then Hand It BackMeasure the change with the same tools that found the fault, separate what is fixed from what is not, write the incident note, pass each remaining item to its owner and give back your access.9 min