Cron Expression Generator
A practical reference for teams that need to build a readable cron schedule from plain requirements.
Cron Expression Generator from Sandglass helps you build a readable cron schedule from plain requirements. Use the result to decide what to monitor continuously.
When to reach for this tool
Reach for this when you need to build a readable cron schedule from plain requirements during setup, debugging, or an incident review. A one-off check is useful for diagnosis, but production systems need continuous monitoring once the immediate question is answered.
- Design the schedule before writing the job, not after.
- Prefer a readable expression over a clever compact one.
- Pair every scheduled job with an owner and a heartbeat.
From one-off check to continuous monitor
Use the generator to design the schedule first, then document the job owner and attach a heartbeat that fires after the job completes its work successfully.
- Recreate the same check in Sandglass on an interval so the next change is caught without re-running the lookup.
- Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever fixes the problem.
- Track the result over time instead of treating one manual reading as the final answer.
Why a lookup is not monitoring
A clever expression is worth less than a clear one. Favor a schedule the next engineer can read over a compact string that hides when the job truly runs.
Use this tool well
Step 1: Run the check and read the result
Use the output to confirm the current state, and treat anything surprising as a starting point for diagnosis rather than a verdict.
Step 2: Define what healthy means
Write down which results count as healthy, degraded, or failed before you automate anything.
Step 3: Promote it to a continuous monitor
Recreate the same check in Sandglass on an interval so the next change is caught automatically.
Step 4: Route the alert to an owner
Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever will fix them.