Laravel Schedule Monitor Laravel Package

Product Decisions This Supports

• Observability & Reliability: Enables tracking of scheduled tasks (e.g., cron jobs, Laravel tasks) to proactively detect failures, delays, or performance degradation. Critical for SLA compliance (e.g., "99.9% uptime for scheduled reports").
• Build vs. Buy: Buy—avoids reinventing logging/alerting for scheduled tasks. Reduces dev effort vs. custom solutions (e.g., logging to files + external monitoring).
• Scalability: Supports multi-tenant Laravel apps (via spatie/laravel-multitenancy) without tenant-aware job conflicts.
• Integration with Oh Dear: Extends monitoring to third-party alerting (Slack, SMS, etc.) for missed/failed tasks, reducing tooling complexity.
• Compliance/Audit: Logs execution metrics (runtime, memory) for post-mortems or regulatory audits (e.g., "Prove backup jobs ran weekly").
• CI/CD Pipeline: Automates syncing schedules post-deploy (schedule-monitor:sync) to ensure monitoring stays in sync with code changes.
• Cost Efficiency: Free (MIT license) with optional paid support from Spatie, avoiding vendor lock-in.

When to Consider This Package

• Avoid if:
  • You need real-time dashboards (this is log-based; pair with tools like Grafana for visualizations).
  • Your tasks are stateless or idempotent (no need to track execution).
  • You’re using non-Laravel scheduling (e.g., Kubernetes CronJobs, AWS EventBridge).
  • You require sub-minute granularity (grace time is in minutes).
• Consider alternatives if:
  • You need distributed tracing (e.g., OpenTelemetry) for microservices.
  • Your stack is non-PHP (e.g., Node.js, Python).
  • You need predictive alerts (e.g., ML-based anomaly detection) beyond simple timeouts.
• Look elsewhere for:
  • Advanced analytics (e.g., trend analysis of task durations).
  • Multi-cloud scheduling (e.g., AWS Step Functions + CloudWatch).

How to Pitch It (Stakeholders)

For Executives:

"This package turns Laravel’s scheduled tasks into a self-monitoring system—like a heartbeat for your backend. It logs every task’s start, failure, or delay, and integrates with Oh Dear to alert us if something goes wrong (e.g., a nightly report misses its window). For $0, we get visibility into critical jobs without adding engineering overhead. Think of it as insurance for your cron jobs—proactive, not reactive."

Key Outcomes:

• Reduce downtime from undetected task failures.
• Automate compliance checks (e.g., "Did the tax report run?").
• Cut mean-time-to-resolution (MTTR) for scheduling issues.

For Engineering:

*"This is a drop-in solution for monitoring Laravel’s Schedule facade. It:

1. Logs everything: Execution time, memory, success/failure.
2. Alerts via Oh Dear: Slack/email notifications for missed tasks (configurable grace periods).
3. Zero boilerplate: Just run composer require spatie/laravel-schedule-monitor, publish migrations, and add schedule-monitor:sync to your deploy script.
4. Extensible: Custom names, ignore tasks, or store command output in the DB.

Trade-offs:

• No real-time UI: Logs are DB-based (use schedule-monitor:list or build a simple admin panel).
• Oh Dear dependency: If you’re already using it, this is a natural extension. Otherwise, the core logging works standalone.

Action Items:

1. Add to composer.json and run migrations.
2. Integrate schedule-monitor:sync into deploy pipelines.
3. Set up Oh Dear alerts (optional but recommended).

Example Win: "We caught a failing backup:run job before it caused a production outage—alerted via Slack in 2 minutes."