Integrations
Works with every environment
CronObserver accepts a simple HTTPS check-in. If your platform can make an HTTP request, you can monitor it.
Linux / Unix Cron
Add a curl call after your script finishes and include grace periods to avoid noisy alerts.
0 * * * * /app/scripts/report.sh && \ curl -fsS -X POST https://cronobserver.com/checkin/<token>
Kubernetes CronJob
Wrap your job container and call the check-in endpoint once the work is done.
apiVersion: batch/v1
kind: CronJob
metadata:
name: report-job
spec:
schedule: "*/30 * * * *"
jobTemplate:
spec:
template:
spec:
restartPolicy: Never
containers:
- name: worker
image: alpine:3
command: ["sh", "-c", "run-task && curl -fsS -X POST https://cronobserver.com/checkin/<token>"]Laravel Scheduler
Use onSuccess hooks to send the heartbeat only when the artisan command completes successfully.
Schedule::command('reports:daily')
->daily()
->onSuccess(fn () =>
Http::post('https://cronobserver.com/checkin/<token>')
);Node.js / Fetch
Await your job promise, then fire a POST request to confirm the run.
await runJob();
await fetch('https://cronobserver.com/checkin/<token>', {
method: 'POST'
});CI Pipelines
Use curl or HTTP libraries in GitHub Actions, GitLab CI or any pipeline after the final step.
- name: heartbeat
run: |
curl -fsS -X POST https://cronobserver.com/checkin/<token>Need a specific stack?
Drop us a message with your stack or scheduler. We maintain lightweight guides for the most common cron, serverless and queue platforms.