PROBLEM
A service lives on one box, nobody can rebuild it from notes, and logs land wherever they fell.
PODEJŚCIE
Hard configuration, a place for logs, and a procedure you can repeat.
SCOPE
- install and baseline
- network services
- logging and rotation
- rebuild notes
DELIVERABLE
- configuration in scope
- rebuild note
- log path
PROCESS
- inventory
- baseline
- service
- reboot check
System administration starts where “it kind of works” ends: kernel, service, disk, time, logs. Without that, SIEM and scripts only decorate the mess.
A host should return to a known state after reboot. If it does not — that is the scope, not “DevOps magic”.