Crontab → systemd timer.
cron jobs run in the dark — no logs, no status, no catch-up. Paste a crontab line and get an equivalent systemd service + timer: supervised, logged in the journal, and visible with one command.
Out of the dark
A cron job that fails at 3am fails silently — the output goes nowhere you'll look, there's no record it even ran, and if the box was down at 3am the run is simply lost. A systemd timer fixes all three: the run is a unit with its output in the journal, systemctl list-timers shows you the last and next fire, and Persistent=true catches up a run missed during downtime. Same schedule, far more visibility.
That visibility points to a bigger need: identifying which scheduled work reported a result on the configured managed hosts and noticing missing evidence. A control plane can contribute that scoped view, but it does not prove execution across every host.
Scheduled, supervised, visible.
For configured managed jobs, Infraveil can report selected schedule, process, and result evidence. Host jobs outside the managed contract remain outside that view, and the evidence does not guarantee completeness or explain every failure.
See how it works