dply/queue-insights

dply Queue driver and queue job lifecycle reporting for Laravel.

v1.1.1 2026-08-27 16:35 UTC

Requires

• php: ^8.2
• illuminate/http: ^11.0|^12.0|^13.0
• illuminate/queue: ^11.0|^12.0|^13.0
• illuminate/support: ^11.0|^12.0|^13.0

MIT

• queue
• laravel
• dply

Published on Packagist.org on 2026-08-27 16:36 UTC

README

Reports Laravel queue job lifecycle events to dply.

Queue depth, waiting jobs and failures can all be read straight from the queue store, and dply reads them without this package. What no external observer can see is execution: how long a job took, whether it succeeded, and what a job class's throughput looks like. A completed job deletes its own row, so by the time anything polls, the evidence is gone.

Only the application is present at that moment. That is one of the two things this package does.

The other is the dply queue driver — the client for dply's managed queue.

Install

composer require dply/queue-insights

The service provider is auto-discovered. The package is inert until dply configures an endpoint and token — with neither set it registers no listeners at all, so installing it costs a stopped application nothing.

dply installs and configures this for you when queue insights are enabled for a site, or when a site is moved onto the managed queue. You do not normally require it by hand.

The dply queue driver

Set these and QUEUE_CONNECTION=dply resolves. There is no config/queue.php edit — the package registers the connection when DPLY_QUEUE_URL is present:

QUEUE_CONNECTION=dply
DPLY_QUEUE_URL=https://dply.io/api/queue/v1
DPLY_QUEUE_TOKEN=your-token

Optional: DPLY_QUEUE_DEFAULT (default queue name, default) and DPLY_QUEUE_RETRY_AFTER (seconds a reserved job stays invisible, 90).

If your application declares its own dply connection, the package leaves it alone.

Why not the sqs driver

dply's endpoint speaks the SQS wire protocol, so Laravel's own sqs driver does talk to it. It costs two things this driver does not:

1. The AWS SDK. aws/aws-sdk-php becomes a dependency of your application, to reach a service that is not Amazon's.
2. Your AWS credentials. The stock sqs connection reads AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY — the same variables your S3 disk uses. Pointing those at dply would break your filesystem to fix your queue.

dply's endpoint accepts a bearer token as readily as a request signature, so this driver is plain HTTP: no SDK, no signing, no AWS-shaped variables.

Configuration

env	default	meaning
DPLY_QUEUE_INSIGHTS_ENDPOINT	—	Where events are POSTed. Unset disables the package.
DPLY_QUEUE_INSIGHTS_TOKEN	—	Bearer token for that endpoint. Unset disables the package.
DPLY_QUEUE_INSIGHTS_BUFFER	50	Events held in memory before the oldest are dropped.
DPLY_QUEUE_INSIGHTS_TIMEOUT	2.0	Seconds allowed for the flush request.

What it sends

For each job: name, queue, connection, attempt count, and duration in milliseconds. For failures, additionally the exception class and the first 500 characters of its message.

It does not send job payloads. A payload carries whatever your application was handed — often customer data — and shipping that off the box to make a dashboard prettier is not a reasonable trade.

Design rules

The package runs inside your queue workers, so it is built to be impossible to notice:

1. It never throws. An exception raised in a queue-event listener fails the job. Monitoring must not cause the outage it reports.
2. It never blocks. Events buffer in memory and flush once, on shutdown. A slow or dead endpoint costs a worker one timeout per process, not per job.
3. It never grows without bound. A full buffer drops the oldest events rather than consuming memory a worker is running under a --memory cap for.

Requirements

PHP 8.2+, Laravel 11, 12 or 13.

License

MIT.