Troubleshooting Method and Monitoring

You will be able to

• Apply a repeatable loop (observe, hypothesise, test, change one thing, verify, record) to any fault.
• Find the answer to a configuration question using only the manuals and files on the machine.
• Read CPU, memory, disk, I/O and network figures and say which resource is the bottleneck.
• Set up the web console for monitoring and use its logs, services and metrics pages.

Lessons

1. 01A method for troubleshooting, and answers from the machine itselfUse a fixed loop to turn a vague complaint into a tested cause, and find documentation without a browser.systemctljournalctldmesgmanman -krpm -qd0/3 exercises
2. 02Monitoring a system's vital signsRead CPU, memory, disk, I/O and network figures with the USE method, and tell which resource is the bottleneck.uptimevmstattopfreeiostatsar0/3 exercises
3. 03Monitoring and troubleshooting with the web consoleEnable the web console, open its firewall port, record metrics history and use its logs, services and storage pages.cockpitsystemctl enable --now cockpit.socketfirewall-cmd --add-service=cockpitcockpit-pcppmloggerss -tlnp0/3 exercises