JobPulse auto-discovers every @Scheduled and Quartz job in your Spring Boot app, tracks each run, and alerts you the moment a job fails — or never runs at all.
dependencies { // one dependency, that's it implementation 'io.jobpulse:jobpulse-spring-boot-starter:0.1.0' }
jobpulse: api-key: ${JOBPULSE_API_KEY} alert-email: ops@yourcompany.com # every @Scheduled job is now monitored.
No curl commands. No ping URLs to paste. Zero code changes.
Backups, reports, data syncs, cleanups — they only make news when they fail. JobPulse makes sure you hear about it in minutes, not weeks.
The starter registers every @Scheduled and Quartz job on startup. New jobs appear in your dashboard automatically — no setup per job.
A job that never starts is worse than one that fails loudly. JobPulse alerts you when a job misses its expected schedule — the failure mode cron is blind to.
See every execution: success, failure, duration, and trends. Spot jobs that are getting slower before they start timing out in production.
Email and Slack first. Then SMS, then a phone call that keeps ringing until someone acknowledges. Alerts should be as loud as the failure.
The Spring Boot starter is fully open source. Audit every line of what it sends, or self-host your checks against the hosted dashboard.
The starter sends only job names, status, and timing metadata — never your business data. Open source, so you can verify every byte.
Three steps. If you can add a dependency, you can monitor your jobs.
One Gradle or Maven dependency. Compatible with Spring Boot 3.x, Java 17+.
Drop jobpulse.api-key into application.yml. The starter handles the rest on startup.
Every scheduled job shows up automatically with live status, history, and alerts.
Generic cron monitors are great — until you have 40 jobs and realize every one needed a hand-pasted curl command.
| Generic ping-URL tools | JobPulse | |
|---|---|---|
| Setup per job | Manual curl / ping URL | Automatic |
| Job discovery | You list every job | Auto-detected on startup |
| Failure details | Silence only | Exceptions, duration, trends |
| New jobs added later | Must remember to monitor | Covered automatically |
| Works outside Spring | Any cron | Spring Boot first, ping fallback |
Free while in beta. Beta users lock in 30% off for life.
They're excellent generic tools, but each job needs a manually-pasted ping URL, and they only see "did a ping arrive." JobPulse is native to Spring Boot: it auto-discovers your jobs, captures real failures with stack traces, tracks durations, and covers new jobs automatically. You can still send standard pings for non-Spring jobs — JobPulse accepts those too.
Only job metadata: name, cron expression, execution status, duration, and error class with stack trace. The starter is open source, so you can verify exactly what's sent. Your business data never leaves your servers.
No. Reports are batched and sent asynchronously on a background thread with graceful degradation — if JobPulse is unreachable, your jobs run exactly as before. Overhead per job run is microseconds.
Quartz job auto-discovery is in the beta. @Async and messaging-based scheduling are on the roadmap — beta users vote on what ships next.
The starter is and always will be open source. A self-hostable dashboard is planned for the Business tier. During beta, everything runs on the hosted service.
Join the beta and lock in 30% off for life. We invite users in small batches so everyone gets a working setup.