PHPackages                             gilbitron/laravel-queue-monitor - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. gilbitron/laravel-queue-monitor

ActiveLibrary[Queues & Workers](/categories/queues)

gilbitron/laravel-queue-monitor
===============================

A Laravel package to monitor queue jobs.

1.0.0(9y ago)1111.8k↓50%4[3 issues](https://github.com/gilbitron/laravel-queue-monitor/issues)MITPHP

Since Jan 17Pushed 9y ago1 watchersCompare

[ Source](https://github.com/gilbitron/laravel-queue-monitor)[ Packagist](https://packagist.org/packages/gilbitron/laravel-queue-monitor)[ RSS](/packages/gilbitron-laravel-queue-monitor/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (1)DependenciesVersions (2)Used By (0)

Laravel Queue Monitor
=====================

[](#laravel-queue-monitor)

A Laravel package to monitor queue jobs. Logs certain information about [queue jobs](https://laravel.com/docs/5.3/queues) in a database table:

- The elapsed time of the job including start and finish timestamps
- If `--tries` is being used the attempt number for each job
- If the job failed and the exception given (if available)
- Custom data (optional)

Requirements
------------

[](#requirements)

- Laravel 5.3+

Install
-------

[](#install)

Install the composer package:

```
composer require gilbitron/laravel-queue-monitor
```

Add the service provider in `config/app.php`:

```
/*
 * Package Service Providers...
 */
Gilbitron\LaravelQueueMonitor\LaravelQueueMonitorProvider::class,
```

Run a migration to setup the `queue_monitor` database table:

```
php artisan migrate
```

Usage
-----

[](#usage)

All queue jobs will now be monitored and results stored to the `queue_monitor` database table. No other configuration is required.

### Custom Data

[](#custom-data)

To save custom data with the queue monitor results you need to include the `QueueMonitorData` trait in your Job and use the `saveQueueMonitorData()` method. For example:

```