Monitor Log Rotation & Cleanup Cron Jobs
Stop disk-full outages caused by unrotated logs
The problem
Log rotation runs silently every night. When a config change breaks logrotate, logs pile up for weeks. You discover it when the disk fills up at 3 AM and the application crashes — the worst kind of preventable outage.
# Nightly log rotation + old file cleanup
$ crond-agent wrap --name "log-cleanup" -- /etc/cron.daily/logrotate
[crond.io] monitoring "log-cleanup" (every 24h)
[crond.io] ping sent ✓ (exit 0, 4.2s)
[crond.io] ping sent ✓ (exit 0, 3.8s)
# Config error after package update
[log-cleanup] error: /var/log/nginx/*.log: No such file or directory
[crond.io] FAILURE ping — exit code 1
[crond.io] webhook fired → https://hooks.slack.com/...
How crond.io helps
crond-agent monitors every logrotate execution. A broken config triggers an immediate alert, giving you time to fix it long before disk usage becomes critical.
- ✓Immediate alerts when logrotate fails due to config errors
- ✓Catch broken rotation before disk usage spirals
- ✓Exit code reporting identifies the exact failure reason
- ✓Works with logrotate, custom cleanup scripts, tmpwatch/tmpreaper
- ✓Duration tracking catches rotation jobs that are taking too long
Start monitoring in 60 seconds
Free tier includes 10 monitors. No credit card required.
$get-started --free