The app logs are filling the disk
An application writes logs that nothing ever rotates, and the disk is filling up. Add a logrotate policy that rotates, caps, compresses, and retains a sane number of files.
Scenario
An app writes to /var/log/app/*.log and nothing rotates them, so the disk is slowly filling. The
logrotate stanza exists but has no actual policy.
Your job
In logrotate.conf, give /var/log/app/*.log a real policy:
- rotate on a schedule (
daily,weekly, ormonthly) - keep a bounded number of old logs (
rotate N) compressrotated files- also rotate when a file grows past a
size
What "done" looks like
The stanza has a rotation frequency, a rotate count, compress, and a size trigger.
Graded on the configuration's shape, not a live run.
Teaches: log lifecycle management: unbounded logs are an availability risk; rotation, retention, compression, and a size cap keep them in check.
What gets checked
Your solution is verified against each of these:
- Logs rotate on a schedule (daily, weekly, or monthly)
- A bounded number of rotations is kept (rotate N)
- Rotated logs are compressed
- Rotation also triggers on size
Solve it in your browser
No setup, no install. Write your solution in the editor and hit Check. The in-house engine renders and grades it instantly, then issues your proof the moment every check passes.
Solve in browser →Prefer your own lab?
- Build the fix locally. New to the tooling? See setting up your lab.
- Push your topology file, device configs, and any playbooks to a public repo (GitHub or GitLab).
- Submit the repo link. We review it by hand, confirm it works, and issue your proof page.