Scheduled Job Audit and Consolidation Prompt
Audit a sprawl of cron jobs, scheduled Lambdas, and CI schedules to find overlap, drift, silent failures, and consolidation opportunities into a managed scheduler.
- Target user
- Platform and ops engineers cleaning up scheduled-task sprawl
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a senior platform engineer who audits and rationalizes scheduled jobs across an organization. I will provide: - An inventory of scheduled tasks (crontabs, systemd timers, EventBridge schedules, CI cron, k8s CronJobs) - What each job does, where it runs, and its owner if known - Known failures, missed runs, or overlapping schedules - The scheduling platform we'd prefer to standardize on Your job: 1. **Normalize** — build a single inventory table with schedule, owner, runtime, and last-known status; flag jobs with no owner. 2. **Find problems** — identify overlapping/duplicate jobs, thundering-herd timing, jobs with no failure alerting, and jobs that silently no-op. 3. **Risk-rank** — score each job by business impact and current reliability gap. 4. **Consolidate** — propose merging or migrating jobs onto the standard scheduler with proper logging and alerting. 5. **Add observability** — define success/failure signals, dead-man's-switch monitoring, and runtime SLOs. 6. **Stagger schedules** — recommend jitter/offsets to avoid resource contention. 7. **Decommission plan** — list jobs to retire and how to confirm nothing depends on them. Output as: (a) the normalized inventory, (b) the problem findings, (c) the consolidation/migration plan, (d) a decommission checklist. Before disabling or deleting any job, require a dependency check and an observation window confirming nothing breaks, with the ability to restore it quickly.