Schedule watch
Know when a cron, timer, or CronJob is late, missed, or still running.
JobWatch monitors cron, Kubernetes CronJobs, backups, and pipelines, and tells you when a run is late, missed, or failed.
Install an agent, add a Helm chart, or put a single heartbeat URL at the end of a script. JobWatch keeps the schedule, the last run, and the reason it failed.
Know when a cron, timer, or CronJob is late, missed, or still running.
Exit codes, timeouts, and missed windows are decided by the schedule.
Related failures group into one incident instead of a pile of pages.
Stdout and stderr sit next to the run that produced them.
CronJobs, pods, and warning events from the cluster agent.
Slack, email, Teams, and webhooks with quiet hours and de-duplication.
Ask why a job failed. It reads the evidence and does not change your systems.
Publish a public page for the jobs your customers depend on.
Linux and Kubernetes agents, with a heartbeat URL when you cannot install one.
Success rate, runtime drift, MTTD, and the jobs that fail most often.
Roles, API keys, and an audit log for every change.
Run it in your own cluster. Job data stays in your database.
A missed backup should not wait until Monday. JobWatch compares each run with its schedule, expected duration, and exit code, then opens one incident when several jobs fail together.
“The nightly backup had been skipping for nine days. A missed run now reaches us in minutes.”
“We replaced a wiki of cron entries with an inventory that discovers itself.”
“Runtime drift showed up two weeks before the maintenance window would have failed.”
Every new workspace starts with a 14-day Team trial.
Create a workspace, paste an API key or sign in, and the overview shows what needs attention.