Splunk Linux Use Case

Backups You Can Testify Under

Proving backups actually ran

The scenario

The backup job that "always works" failed silently eleven nights ago. restic finished but wrote nowhere; the systemd timer got disabled during that refactor; the borg archive is corrupt at chunk 40%. Insurance, management, and future-you all assume backups run - the only honest answer comes from a system that watches the watcher, on its own clock.

The app recipe

TA-backup Detects restic/borg (and b2/rclone via timers), reports configured jobs + stale timers
TA-cronbeat Every systemd timer and cron entry: total, stale, absent - the heartbeat layer
TA-zfspool The target pool itself: md/btrfs/ZFS state, corruption counters
TA-disk SMART on the backup target disks

Problems this kills

Killer searches

Who this is for

Anyone who has ever been responsible for data and slept through a backup failure window - which is everyone.

Next

All Use Cases Browse All Apps