Cron job monitoring
Give each scheduled job a private ping URL. Run curl against that URL when the job finishes. If Cronward does not receive the expected ping by the end of the grace period, it sends an alert.
Heartbeat pings
Send an HTTP GET or POST request to the monitor's private URL when the job completes. The ping endpoint supports IPv6.
Per-monitor grace periods
Set how long each monitor waits after an expected ping before sending an alert.
Alert delivery
Send alerts by email, SMS, Slack, PagerDuty, Microsoft Teams, Discord, Zapier, or plain webhooks.
Cron and interval schedules
Set when pings are expected with a cron expression or a plain interval such as every 15 minutes.
Public status pages
Publish a status page for an individual monitor so others can check its current status.
Full API with per-key tokens
Use the full API to manage monitoring from scripts and authenticate requests with per-key tokens.
Ping and status endpoints
Use a monitor's private ping URL to record job completion. If you make the monitor public, clients can fetch its status as JSON.
Frequently asked
What happens if a job runs long?
Cronward waits through the monitor's grace period after the expected ping time. If the ping arrives within that window, no alert fires. If the window expires without a ping, Cronward sends an alert.
Can CI schedulers and Windows Task Scheduler send pings?
Yes. Any HTTP client can send a GET or POST request to the monitor's private ping URL.
What happens if the machine is offline when the ping is due?
Cronward sends an alert if the expected ping is still missing when the grace period ends. If the machine sends the ping after reconnecting, Cronward records it as late.
How long does Cronward retain monitoring data?
Data retention depends on your plan.