How is this different from Crontinel?

Most generic monitors tell you a job ran. They have no visibility into Laravel Horizon, queue depth, or whether your supervisor crashed. Crontinel reads the same Redis keys Horizon uses, so it catches failures the outside-in approach misses entirely.

Does Crontinel require code changes?

No. The Laravel package hooks into ScheduledTaskStarting, ScheduledTaskFinished, and ScheduledTaskFailed events automatically. You run composer require and the monitoring starts. No command wrapping, no custom metrics, no configuration required.

Can I self-host Crontinel?

Yes. The package ships with a built-in dashboard at /crontinel that works entirely offline. The SaaS at app.crontinel.com is optional. Either way you own your data.

What alert channels does Crontinel support?

Slack, email, PagerDuty, and webhooks. Webhooks support HMAC signature verification. You can scope channels per app so a critical app pages PagerDuty while others post to Slack.

Crontinel vs Laravel Telescope

Telescope tells you what happened.
Crontinel tells you when something is wrong.

Laravel Telescope is a first-party debug assistant. It records requests, jobs, queries, and exceptions so you can inspect them. It's excellent at that job. But it doesn't alert you, it doesn't monitor thresholds, and it's not meant for production visibility.

What Telescope is for

Telescope is a development and debugging tool. You install it in local or staging environments to inspect what your application is doing: which queries ran, which jobs fired, what the request lifecycle looked like. It's indispensable for development. The Laravel team built it well.

What Telescope is not

Telescope is not a monitoring tool. It has no alerting, no thresholds, no concept of "this queue is too deep" or "this supervisor stopped." It records history you can browse; it does not watch for problems and notify you. If you enable it in production, you're adding overhead for a UI you only open after something breaks.

✗ No alerts of any kind (Slack, email, webhook)
✗ No queue depth or Horizon supervisor monitoring
✗ No configurable thresholds or failure rate tracking
✗ No external visibility (requires VPN or internal access)
✗ Adds database writes for every request in production

The gap in a real scenario

Your Horizon supervisor pauses at 2am. Jobs queue up. No one knows until a customer complains in the morning.

02:14 Horizon supervisor paused (reason unknown)

✗ Telescope: recorded the last job that ran before pause

✗ Telescope: no alert fired

✗ Telescope: queue depth unknown, no threshold to breach

✓ Crontinel: alert fired at 02:14, supervisor paused

✓ Crontinel: Slack notification sent, on-call engineer paged

Capability	Crontinel	Telescope
Slack / email alerts when something breaks	✓	✗
Horizon supervisor + paused state monitoring	✓	✗
Queue depth thresholds and alerts	✓	✗
Oldest pending job age	✓	✗
Failed jobs per minute with alerting	✓	✗
Scheduled job run history	✓	✓
Job payload and exception inspection	✗	✓
Query, request, log inspection	✗	✓
Works in production without overhead risk	✓	✗
External dashboard (no VPN needed)	✓	✗
Open source	✓	✓

Use both, for different jobs

Telescope is a great development companion. Keep it in local and staging. Crontinel is your production watchdog. It alerts you before a customer does. They serve completely different purposes and there's no reason to choose between them.