Pulse (Heartbeat) Checks

Checks & Monitoring Updated Apr 2, 2026

Pulse checks work in reverse: instead of Chglog pinging your server, your server pings Chglog. This is perfect for monitoring cron jobs, background workers, scheduled tasks, and any service that runs on a schedule.

How it works

  1. Create a Pulse check and configure the expected interval — the maximum time Chglog should wait between pings.
  2. Chglog generates a unique endpoint URL (e.g. https://pulse.chglog.com/{team_token}/{check_token}).
  3. Your service sends an HTTP request (GET, POST or HEAD) to that URL at the end of every successful run.
  4. If Chglog doesn't receive a ping within the expected interval, the check is marked down.

Interval format

Pulse intervals use natural-language expressions instead of fixed dropdowns. Examples:

  • 5 minutes
  • 1 hour
  • 25 hours
  • 2 days 6h

Minimum: 15 seconds. Maximum: 35 days.

Regenerating the endpoint token

If your endpoint URL is compromised, you can regenerate the token from the check detail page. The old URL will stop working immediately. Update your service to use the new URL.

Credits

Each ping to the Pulse endpoint costs 1 credit. This is deducted from your team's balance when the ping is received.

Example: monitoring a cron job

curl -fsS --retry 3 https://pulse.chglog.com/abc123/def456

If the backup fails and curl never runs, Chglog will detect the missed heartbeat and alert you.

Back to Checks & Monitoring