Failure signal
A CronJob is suspended or fails to create a pod.
KUBERNETES INTEGRATION
Monitor Kubernetes CronJobs beyond pod status
Kubernetes exposes pod and job status, but a small external heartbeat can answer whether a scheduled workload completed its useful work on time.
Job runs↓
Heartbeat sent↓
Upnora receives it✓
GET /h/YOUR_KEY/YOUR_TOKENWHAT CAN FAIL
Why this job can stop silently.
Failure signal
The container starts but the task exits before completion.
Failure signal
A dependency or cluster problem prevents the workload from reporting.
BASIC INTEGRATION
Send the heartbeat after successful work.
Use the unique GET URL provided by your Upnora dashboard. The examples are generic: replace them with your monitor URL and keep it in an environment variable or secret.
run_the_scheduled_task && curl --fail --max-time 10 "$UPNORA_HEARTBEAT_URL"IMPLEMENTATION NOTES
Keep the signal meaningful.
Run the heartbeat command at the end of the container script, after the workload succeeds. Store UPNORA_HEARTBEAT_URL in a Kubernetes Secret.
See scheduled task monitoring →Common mistake
Do not send the heartbeat at container startup. Startup only proves that a pod began; the final call proves that work completed.
Wrong: heartbeat → run the job
Better: run the job → heartbeat
MORE HEARTBEAT INTEGRATIONS
Use Upnora with your stack.
FAQ
Kubernetes heartbeat monitoring, simply explained.
How do I monitor a Kubernetes CronJob?
Call the Upnora heartbeat URL from the container after the task completes.
Where should I store the URL?
Use a Kubernetes Secret and expose it as an environment variable.
Does Upnora replace Kubernetes monitoring?
No. It adds a simple external heartbeat for scheduled workloads.
ADD A SUCCESS SIGNAL