cron or systemd timers
Both run things on a schedule. One of them tells you when it failed.
Writing
Running Linux servers well: systemd, networking, storage, logs and the tools that show what a machine is really doing.
Both run things on a schedule. One of them tells you when it failed.
A sequence that finds the cause in about a minute, including the case where df and du disagree.
It is not a percentage, and a load of 8 may be perfectly healthy.
The order of operations matters more than the settings.
The default rotation method silently breaks with any process that holds its log open.
Most people use a fraction of it and miss the parts that make it fast.
Get this wrong and the service either restarts forever or is reported dead while running.