Celery monitoring

Release availability

Checked 2026-09-20. Celery SDK connections are temporarily unavailable. Use manual HTTP reporting below. This setup does not discover scheduled tasks automatically.

Set up with HTTP now

No CronRadar package installation is needed. Add this report after your existing scheduled job completes successfully. This is manual reporting: each job needs its own key and real schedule, and no scheduler registry is discovered automatically.

Set CRONRADAR_API_KEY in your deployment's secret manager. Create a separate CronRadar application and API key for production, staging, and development. Never paste the real key into an AI prompt, commit it, or print it.

export CRONRADAR_API_KEY='<your saved CronRadar API key>'

curl --fail --silent --show-error --max-time 5 \
  --user "$CRONRADAR_API_KEY:" \
  "https://cron.life/api/v1/ping/daily-backup?schedule=0%202%20*%20*%20*" || true

Replace daily-backup and the example daily 02:00 UTC schedule with the job's stable key and real schedule. Keep the schedule on each report so a deleted monitor can register again. The five-second timeout and || true keep a monitoring outage from failing the job. A successful-completion heartbeat detects missed completions; add start/fail lifecycle calls if you need explicit failures or stuck-run detection.

Verify the first run

Run the real job once and confirm a successful execution in its CronRadar application. Monitoring is not verified by copying these instructions. Then run a labeled alert test and confirm delivery at the destination.

See the HTTP API reference for Basic authentication, schedules, timezones, and lifecycle events. The machine-readable contract is OpenAPI.