Use cases · Monitoring
Monitoring and uptime cron jobs
Health-check work splits two ways: actively pinging services on a clock, and proving that a flow you run elsewhere still runs. The spokes here cover both.
About this topic
Monitoring
Monitoring sits in two adjacent boxes. Active monitoring is where Crontap pings your endpoints, records response times and status codes, and alerts when something drifts. The api-health-checks and uptime-monitoring spokes cover that pattern: 1-minute paid pings, response charts over 90 days, and alert routes to email or webhook. Passive monitoring uses native Crontap Heartbeats: a job running anywhere checks in, and Crontap alerts by email or generic JSON webhook when that check-in is late or reports failure.
Both share one Crontap dashboard and 90-day history. Scheduled calls also keep per-run status code and duration, with automatic retries before failure alerts. Native heartbeats are the simple default for dead-man monitoring. Keep Healthchecks.io, Cronitor, or another external receiver alongside Crontap only when your risk model requires the scheduler and alerter to fail independently.
Use cases on Monitoring
3 itemsRelated on Crontap
The same Monitoring topic, from other angles.
FAQ
Common questions on Monitoring
- Crontap vs Healthchecks.io: which do I use?
- Use Crontap when you want schedules, uptime monitors, and native heartbeats in one product. Healthchecks.io remains a stronger fit for self-hosting, start and duration signals, log signals, or cron-expression expectations. Use both only when an independent watcher must stay outside the scheduling system.
- Can Crontap replace UptimeRobot?
- For straightforward HTTP up-down checks at minute or 5-minute cadence, the uptime-monitoring spoke covers it. For SMS alerts, third-party page integrations, and 30-second cadence, UptimeRobot has more depth on the monitoring-only feature surface. Often teams use Crontap for scheduled work and Crontap's uptime feature for the basic up-down, and bring a dedicated tool for tier-1 paging.
- How granular is the run log?
- Per-fire: timestamp, response status, duration in milliseconds, response size, and error summary. Useful for spotting 'the cron is firing on time but my endpoint is taking 12 seconds when it used to take 200ms' kind of drift.
More from Crontap
Topics across the site.
Every topic Crontap covers, in one row. Each one has its own page on the use cases surface.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s