Download the PHP package cronitor/laravel without Composer
On this page you can find all versions of the php package cronitor/laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package laravel
Cronitor Laravel
Laravel integration for Cronitor scheduler provisioning and runtime telemetry.
Installation
Publish config:
What it does
- Provisions monitors from Laravel scheduler definitions at deploy time.
- Sends runtime telemetry for scheduled tasks (
run,complete,fail). - Sends runtime telemetry for queue jobs (
run,complete,fail).
Settings reference
enabled
- Type:
bool - Default:
true(CRONITOR_ENABLED) - Global on/off switch for the package.
api_key
- Type:
string - Default:
null(CRONITOR_API_KEY) - Required for
cronitor:syncand runtime telemetry pings.
api_version
- Type:
string|null - Default:
null(CRONITOR_API_VERSION) - Optional API version passed to the Cronitor client.
environment
- Type:
string|null - Default:
null(CRONITOR_ENVIRONMENT) - Optional environment tag passed to the Cronitor client.
monitor_defaults
- Type:
array - Default:
[] - Default fields merged into every monitor created by
cronitor:sync. - Common fields:
notify(string[]) notification list keys.group(string) Cronitor group key.
- Reserved fields are ignored from this block:
key,type,name,schedule.
ignored_jobs
- Type:
string[] - Default:
[] - Skip queue telemetry for matching queue raw names or resolved keys.
ignored_tasks
- Type:
string[] - Default:
[] - Skip scheduler sync and scheduler telemetry for matching task summary or key.
Example:
Sync behavior
Sync is a deploy-time operation. It creates/updates Cronitor monitors directly from Schedule::events() so they appear in the dashboard immediately, before first execution. The sync payload includes each task's monitor key, display name, and cron schedule.
Dry run:
Apply sync:
Runtime telemetry behavior
Scheduler events
ScheduledTaskStarting->runScheduledTaskFinished->completeScheduledTaskFailed->fail
Queue events
JobProcessing->runJobProcessed->completeJobFailed->fail
Deploy flow (recommended)
- Deploy code with
cronitor/laravelinstalled. - Run
php artisan cronitor:syncduring deploy. - Start/continue scheduler and queue workers. Runtime telemetry updates provisioned monitors.
Docker testing
Run the package tests fully in Docker:
Custom queue key contract
If your queued object implements Cronitor\Laravel\Contracts\DefinesCronitorKey, that key is used.
Additional docs
docs/architecture.mddocs/rollout-checklist.md
All versions of laravel with dependencies
cronitor/cronitor-php Version ^1.0
illuminate/cache Version ^10.0|^11.0|^12.0
illuminate/console Version ^10.0|^11.0|^12.0
illuminate/contracts Version ^10.0|^11.0|^12.0
illuminate/events Version ^10.0|^11.0|^12.0
illuminate/queue Version ^10.0|^11.0|^12.0
illuminate/support Version ^10.0|^11.0|^12.0
psr/log Version ^1.1|^2.0|^3.0