Monitoring

    Heartbeat & Cron Job Monitoring

    Monitor cron jobs, background tasks, and scheduled scripts with ping URLs.

    Updated 2026-03-23
    1 min read
    heartbeat
    cron
    ping

    Heartbeat & Cron Job Monitoring#

    Heartbeat monitoring works in reverse — instead of us checking your service, your service pings us. If we stop hearing from it, we know something is wrong.

    How It Works#

  1. Go to Heartbeats in the sidebar
  2. Click Create Monitor — give it a name, set the expected interval and grace period
  3. Copy the unique ping URL
  4. Add \curl -fsS --retry 3 https://lemwatch.com/api/heartbeat/your-slug > /dev/null\ to the end of your script

    5. Configuration#

  5. Expected Interval: How often your job should run (1 min to 24 hours)
  6. Grace Period: Extra time before we alert (handles natural timing variance)
  7. Status: Up (pinging on time), Down (missed ping), Pending (never pinged)

    8. Use Cases#

  8. Cron jobs and scheduled tasks
  9. Database backup scripts
  10. Data pipeline stages
  11. Kubernetes liveness probes
  12. CI/CD pipeline completion checks
    13. Was this article helpful?

    Previous

    Daily Briefing & Priority Dashboard

    Next

    Keyword Monitoring

    Related Articles

    Gzip / Brotli compression check

    Verifies your server compresses HTML, CSS, JS, and JSON responses — up to 80% payload reduction that costs nothing to enable.

    Cache-Control header check

    Grades your Cache-Control headers on static assets, HTML, and API responses — bad caching is a leading hidden cause of slow LCP.

    How do I monitor a JSON API endpoint?

    Add any HTTP endpoint under API Monitoring and Lemwatch checks status code, response time, and optional JSON body assertions every minute.

    How does API endpoint degradation alerting work?

    Lemwatch compares each endpoint's current response time against a rolling 24-hour baseline and alerts when it degrades by 2× or more.

    Back to Help Center