Garmingo Docs
Types

Heartbeat (Cron)

Validate scheduled jobs by requiring periodic heartbeat calls within a defined interval.

Heartbeat monitors allow you to supervise external jobs, schedulers, or workers that run outside of Garmingo. Instead of Garmingo polling your system, your system sends a heartbeat call to confirm liveness.

Flow

  1. Create monitor with type heartbeat.
  2. A unique heartbeatToken is generated and stored in metadata.
  3. After each successful job run, POST or GET the heartbeat endpoint (UI exposes full URL pattern) including the token.
  4. If the expected heartbeat doesn’t arrive within TTL + grace (internal logic), the monitor flips to Unhealthy.

Settings

FieldDescription
schedule(Documentation / descriptive) Cron expression or human note of expected cadence. Not yet enforced.
ttlAcceptable interval between heartbeats (seconds).

Retries are disabled—missing a heartbeat is a single definitive signal.

Status Labels

  • Healthy (good) – recent heartbeat received
  • Unhealthy (Missed) (bad) – overdue heartbeat

Tips

  • Use different tokens per job for isolation.
  • Combine with incidents to trigger notifications when a background pipeline halts.