Monitoring that explains what happened
Heartbeat monitoring for scheduled jobs
A successful schedule entry does not prove a job finished. Send a heartbeat after successful work and alert when the next expected signal is missing.
Signal successful completion
Call your private heartbeat URL only after the job succeeds. Keep the token out of logs and public repositories. A failed task should not send a success signal.
Set an interval and grace period
Match the expected interval to the job schedule and allow for normal execution time. Inspect the first received signal before relying on missed-heartbeat alerts.
Investigate missing signals
Compare the last heartbeat with scheduler logs and job duration. A missing signal can mean a failed job or a delivery failure; investigate both.
Common questions
Does Login2Cloud run my job?
No. Your scheduler runs the job; Login2Cloud observes the signals you send.