A drop-in Composer package that ships wait time, throughput and failure rate from every queue your Laravel app uses — Redis, database, beanstalkd, SQS — to HostAtlas. No exporters to keep alive, no metrics endpoint to maintain, no payload data leaving the host.
Pair the app afterwards with php artisan hostatlas:enrol --key=YOUR_INSTALL_KEY.
Generate keys in Settings → Install Keys.
A single "queue size" gauge is the gas-station fuel-light of monitoring — it goes off when it's already a problem. Per-queue wait time + failure rate is the actual signal.
Nothing else needs configuring — every Laravel queue your app uses ends up in HostAtlas with these six values, named and tagged automatically.
Same flow you'd use for any first-party Laravel package. No exporters, no extra services, no infrastructure changes.
Pull the package into your Laravel app. Tested with Laravel 10, 11, 12; PHP 8.2+.
Run the enrol command with an install key from your HostAtlas tenant. Queue tracking starts on the next scheduled run.
Three artisan commands and a published config file is the whole API surface.
autoauto = every queue Laravel finds. Pass an explicit array to track only some.{ … }agentagent (recommended — ships via the local agent), direct (outbound HTTPS from the app), or none (collect-only, no shipping).class-onlyclass-only (default — only class names), none (no class names at all), or full (include the failing job ID — never the payload).1.01.0 = every failure, 0.1 = 10 % sample. Useful for very high-failure dev environments.No. Only metadata — queue name, job class, attempt count, exception class. Payload bodies stay on the host, always.
No. Reads from the same sources Horizon does and runs alongside it; the package can power both views without duplicating the load on Redis.
A language-agnostic statsd / OTel exporter is on the roadmap. Today: Laravel 10+ only.
Aggregation runs in a scheduled command (default: every 30 s), not in the worker hot path. Adding it shouldn't change measurable throughput.
Tested with Redis, database, beanstalkd, SQS. Anything Laravel's queue manager treats as a first-class driver should work.
Yes — Apache 2.0 on Packagist. Hostatlas tenant required only for the platform-side dashboards + alerting; metrics can also be exported locally.
Free on Packagist. Surfaces in your HostAtlas fleet automatically once you enrol the app.