— Cron jobs & monitoring
Schedule your cron jobs, check their results and catch failures before they go unnoticed. From APIs to backups – all in one place.
What happens when HTTP 200 comes with an empty result? Try the sample data. No setup or account needed.
Response time: 0–990 ms
Height: response time, scaled per chart. In your dashboard, each bar opens the run details.
Beyond a successful request
An accessible API does not tell you whether an import is complete or its data is up to date. Define the result you expect – Cronpimo checks it.
Check values in JSON responses or make a single follow-up request to a separate status endpoint after your job. Spot failures hidden behind a successful HTTP response.
Check JSON responses and data freshness →
Your feed responds but still serves yesterday’s data? Check timestamps against an age limit you choose and get notified when they exceed it.
A scheduled GET or HEAD check fails? Have a monitor marked as read-only verified from another available location. Both results help you narrow down the failure.
WordPress, API checks, data feeds, backups or SSL certificates: choose your use case and adapt the template. Available checks depend on your plan.
Between executions, too
Expect check-ins from backups, imports or your own scripts. Monitor numeric values such as file counts as well. Start and finish signals can protect a linked cron job from overlapping runs.
Set up backup heartbeat monitoring →
Get reminders before your SSL certificates expire. You choose the days and notification destinations.
Check publicly reachable TCP services, such as your mail server or SSH endpoint.
In your dashboard
| Cron jobs | Schedule | Last 24 runs | Status |
|---|---|---|---|
| Update inventoryexample.com/inventory | Every five minutes*/5 * * * * | Response time: 0–990 ms | Success |
| Generate daily reportexample.com/report | Weekdays at 08:000 8 * * 1-5 | Response time: 0–990 ms | Failure |
| Warm up cacheexample.com/cache | Every 15 minutes*/15 * * * * | Response time: 0–990 ms | Paused manually |
| Synchronize dataexample.com/sync | Every hour0 * * * * | Response time: 0–980 ms | Result unknown |
Incidents
Find out when a task fails and review its cause and history. A recovery notification tells you when it succeeds again.
Assign a group name to related alert rules. Cronpimo groups failures that occur close together and reports full recovery once all affected incidents are resolved.
Run details
Compare a run with the last retained successful run of the same job configuration: response time, HTTP status and agent show you what changed.
Pause jobs or suppress notifications during planned maintenance. Once or on a recurring schedule.
Compare the success rate of your checks across multiple days. View a chart in your dashboard or receive scheduled email reports.
Choose an HTTP request, TCP check or SSL check and set a schedule. With heartbeats, your own script checks in with Cronpimo.
Test requests and checks before activating them. For a heartbeat, send an initial check-in from your script.
See each run’s status, response time and execution location. Open the run details to investigate a failed request.
Connect your team’s notification channel and choose which tasks should notify you about failures and recovery.
Try Cronpimo for free. Compare plans for more jobs and additional monitoring features.
cronpimo
