Weave Code
Laravel Laravel Package
thenpingme/laravel
Laravel package for monitoring scheduled tasks with thenping.me. It sends heartbeats for cron jobs and alerts you when tasks fail, run late, or don’t run at all, helping you catch broken schedules early.
Thenping.me for Laravel connects your application's scheduled tasks to the Thenping.me monitoring service, so a cron job that silently fails never goes unnoticed. Installation is a quick Composer require and a service provider registration; the package then hooks into Laravel's scheduler and reports each task automatically.
- Reports every scheduled command, job, and closure to thenping.me
- Sends alerts when tasks fail, run late, or never start
- Zero-config setup via service provider and environment variables
- Captures run duration and execution history per task
- Plays nicely with Laravel's existing scheduler API
Frequently asked questions about Laravel
- What does thenpingme/laravel do?
- It is a telemetry agent that integrates a Laravel application with the thenping.me SaaS. It listens to Laravel scheduler lifecycle events and sends HTTP heartbeat pings so thenping.me can alert when tasks fail, run late, or never run. It is not a general feature library and does nothing for non-Laravel services.
- How do I install thenpingme/laravel?
- Run composer require thenpingme/laravel, then php artisan thenpingme:setup to write a project UUID and API token into your .env file. A sync command enumerates Kernel::schedule() and registers each task server-side. No schema changes or manual service provider wiring are required.
- Does thenpingme/laravel support Laravel 12 or PHP 8.4?
- The upstream repository is archived and has no path to Laravel 12+ or PHP 8.4. That means no compatibility updates, security patches, or issue triage. Under Composer this becomes a hard blocker at your next major upgrade, and it will likely surface mid-upgrade rather than during planning.
- Is thenpingme/laravel still maintained?
- No, the upstream repository is archived, so there are no security patches or issue triage. The 18 stars and 0 dependents are a weak ecosystem signal, but the archive flag is the decisive maintenance risk. Treat sunset of the SaaS as elevated probability, not tail risk.
- What data does thenpingme/laravel send to thenping.me?
- Heartbeats include task names, cron expressions, run durations, hostnames, environment labels, and failure metadata. That data crosses your perimeter to the vendor's SaaS. In regulated environments this can fail security review on its own, so classify every field before adoption.
- Can a thenping.me outage block my Laravel scheduler?
- Verify whether pings are queued or synchronous before relying on this package. A synchronous HTTP call to a degraded API inside the scheduler loop is a latency and potentially blocking risk. The evaluation flags this as an open question, so check configured timeouts and retries.
- What are the alternatives to thenpingme/laravel?
- Standardize on a URL-ping contract such as Healthchecks-style /ping/<uuid>, Pushgateway, or OTLP, and treat thenping.me as one interchangeable backend. A roughly 50-line in-house listener on the same Laravel scheduler events, posting the same ping, is a credible replacement. This approach also avoids committing to a Laravel-specific agent if part of your estate is not Laravel.
- How do I test thenpingme/laravel in my Laravel app?
- You can fake outbound HTTP with Laravel's HTTP fake to assert heartbeat payloads without hitting the vendor. Focus tests on scheduler event handling, payload shape, and failure behavior during API degradation. Because the package is archived, also test your exit path and consider owning a fork if you adopt it.
- How do I exit thenpingme/laravel if I need to?
- The migration is additive—no schema, cutover window, or backfill—so the reverse path is the one to design before adoption. MIT licensing lets you fork, but someone must own that fork. Build an abstraction first and let the package be one driver, so you are not discovering the exit after the archive becomes a blocker.
- Does thenpingme/laravel monitor queued jobs or only scheduled tasks?
- The package is marketed for scheduled tasks and queued jobs, but the technical evaluation only confirms subscriptions to Laravel scheduler lifecycle events. Verify queued-job coverage in the vendor documentation before relying on it. If queued-job monitoring is essential, confirm the exact integration points and data sent.
Weaver
How can I help you explore Laravel packages today?