01 / Promise
Name the outcome
The scheduled job finishes the maintenance, sync, report, backup, billing, or import outcome inside its expected window.
Cron job monitoring
Cron job monitoring with evidence, not just pings.
Luota watches scheduled jobs and opens one incident when the expected heartbeat or run event does not arrive. It is built for the work that quietly breaks revenue, reporting, billing, imports, and syncs.
Operating spine
The workflow operating spine.
The cron schedule is only the timer. The proof path connects the expected window to the real operational outcome.
02 / Signal
Send the signal
Send a heartbeat for simple completion or run lifecycle events when start, duration, output, and failure summary matter.
03 / Drill
Break it on purpose
Skip one scheduled signal or fail one controlled run to prove the missed-window incident before relying on silence.
04 / Incident
Inspect the bad day
The incident should show schedule, grace window, owner, last good signal, payload evidence, alert route, and runbook.
05 / Handoff
Leave an operator path
Route the owner to rerun, recover, or record the miss with durable history for later review.
Heartbeat or run lifecycle
Use a simple heartbeat when success is enough, or run lifecycle events when you need start, finish, duration, failure summary, output, and payload context.
Operator context
Incidents include owner label, environment, deploy SHA, run history, payload evidence, alert delivery state, and runbook URL instead of just a missed ping.
Token-scoped ingest
Each monitor has its own token. If a token leaks, rotate that monitor without affecting the rest of the workspace.
Migration-friendly
Importers for Healthchecks and Cronitor help move existing cron checks into Luota without rebuilding every monitor by hand.
Need a concrete migration or monitoring pattern? Start with the docs, then adapt the payload to the evidence your operator needs.
Open integration docs