Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small CLI toolkit (bash + the text tools) that turns raw system state into a readable report: parse an auth/web log with grep/sed/awk to rank the top offending IPs and error codes, summarize disk (df/du) and memory (free) headroom, list the heaviest processes, and write a timestamped report under /var/log or ~/reports. Wire it to run on a schedule with a cron entry (get the five time fields right) and have it exit non-zero when a threshold (e.g. disk >90%) is breached.
grep/sed/awk/sort/uniq used idiomatically to extract and aggregate — not brittle one-off hacks.
Composes tools with pipes; redirects stdout/stderr deliberately (>, >>, 2>, 2>&1); report written, not just printed.
A correct cron entry (five fields) or systemd timer; explains when it runs and where output/logs go.
Reads df/du, free, and process load correctly; thresholds drive a meaningful non-zero exit code.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A log-analysis & system-health toolkit ## Goal Build a small CLI toolkit (bash + the text tools) that turns raw system state into a readable report: parse an auth/web log with grep/sed/awk to rank the top offending IPs and error codes, summarize disk (df/du) and memory (free) headroom, list the heaviest processes, and write a timestamped report under /var/log or ~/reports. Wire it to run on a schedule with a cron entry (get the five time fields right) and have it exit non-zero when a threshold (e.g. disk >90%) is breached. ## Acceptance criteria - [ ] Text processing: grep/sed/awk/sort/uniq used idiomatically to extract and aggregate — not brittle one-off hacks. - [ ] Pipes & redirection: Composes tools with pipes; redirects stdout/stderr deliberately (>, >>, 2>, 2>&1); report written, not just printed. - [ ] Scheduling: A correct cron entry (five fields) or systemd timer; explains when it runs and where output/logs go. - [ ] Health logic: Reads df/du, free, and process load correctly; thresholds drive a meaningful non-zero exit code. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.