Kubernetes CronJob Monitoring
A practical reliability guide for platform teams.
Kubernetes CronJob Monitoring from Sandglass: practical guidance for monitoring the business result of a CronJob instead of only watching Kubernetes object state.
What this guide covers
This guide focuses on monitoring the business result of a CronJob instead of only watching Kubernetes object state. The goal is to make the operating decision clear before a stressful incident forces the team to improvise.
- Object status shows scheduling, not business success.
- An external heartbeat survives a cluster-wide problem.
- Pair the heartbeat with cluster events for debugging.
How Sandglass supports the practice
Call a heartbeat from the container after the job completes and pair it with cluster events for debugging when the heartbeat is late. Sandglass supports the continuous side of this work with checks, incidents, alert routing, and public status visibility.
- Back the practices here with HTTP, ping, TCP, content, SSL certificate, and heartbeat checks.
- Route incidents to email, Slack webhook channels, and generic webhooks so the right people respond fast.
- Use a public status page to keep customers informed while the team works the incident.
Common mistakes to avoid
Kubernetes status can show scheduling and pod history, but an external heartbeat proves that the job reached its success path.
Implementation checklist
Step 1: Start from customer impact
Decide which failures in this topic actually reach customers before adding any monitoring.
Step 2: Choose one signal per risk
Match each risk to a single HTTP, content, TCP, SSL certificate, or heartbeat check instead of stacking duplicates.
Step 3: Assign an owner and a channel
Give each alert one owner and one destination — email, a Slack webhook, or a generic webhook.
Step 4: Review after real incidents
Revisit intervals, thresholds, and ownership once a real incident shows what was missing.