From: Priya Nair, operations, Fernhill Garden Supply
"The app server's log disk filled up at 02:10 and the nightly order import couldn't write. Can you free the space safely and find out why it happened? Don't touch data/, and don't delete anything we might need for the post-mortem: compress what you can.
Put what you find in incident/ so I can attach it to the ticket."
Your answer: the disk evidence, the cause, a fixed configuration, compressed rotated logs, an emptied debug trace and a packaged incident folder.
The log volume on an app server hit 100% overnight and writes are failing. Deleting the biggest file is the fast answer and often the wrong one: the live log is still being written, and data must never be touched. This lab works the incident the way a careful on-call engineer would.
You will record the disk state, find the largest files, discover why they grew (a debug log level left on after an investigation), fix the setting without losing the rest of the configuration, empty the debug trace in place because the running process still holds it open, then use the freed space to compress the rotated logs instead of deleting them, and package the evidence with a conclusion.
All eight steps share one workspace, and every check also protects the earlier results and the orders data.
Preserve the evidence before you change anything.