Download the PHP package storviaio/vantage without Composer

On this page you can find all versions of the php package storviaio/vantage. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package vantage

Vantage

Latest Version on Packagist GitHub Tests Action Status GitHub Code Style Action Status Total Downloads License

A Laravel package that tracks and monitors your queue jobs. Automatically records job execution history, failures, retries, and provides a simple web interface to view everything.

Why Vantage?

Vantage records every queue job your application runs and keeps that record in your own database, so you can still answer questions about a job long after it left the queue.

Works with every queue driver. Database, Redis, SQS, Beanstalkd, or anything else. Vantage listens to Laravel's queue events rather than to a specific backend, so you can mix drivers or switch between them and tracking keeps working.

Complete execution history. Every run stores status, queue, connection, duration, memory and CPU usage, exception class, message and stack trace, payload, tags, and the full retry chain — kept for as long as you choose.

Built for debugging, not just watching. Answer "what happened to that job?" days or weeks later. Follow a single failure through every retry attempt. See which job classes fail most often and which exceptions are behind them.

Real performance numbers. Per-job memory and CPU telemetry from production, so slow and memory-hungry jobs are something you measure instead of guess.

Search and filter everything. By status, queue, job class, tag or date range — from the dashboard, or from the JSON API for your own tooling.

Retry from anywhere. The dashboard, the CLI (vantage:retry), or your own code through the Vantage facade.

Stays out of the way. Give Vantage its own database connection, turn off payload storage, sample telemetry, exclude noisy jobs, and prune old history on a schedule — see Multi-Database Support.

Installation

The package will automatically register itself using

Publishing Assets:

Requirements

Features

Universal Queue Driver Support

Works with all Laravel queue drivers - database, Redis, SQS, Beanstalkd, and any other driver. Unlike other monitoring tools that require specific drivers, Vantage tracks jobs from any queue driver and saves all data to your database for persistent tracking and analysis.

Job Tracking

Every job gets tracked in the vantage_jobs table with:

Failure Details

When jobs fail, we store the exception class, message, and full stack trace. Much easier to debug than Laravel's default failed_jobs table.

Visit /vantage/failed to see all failed jobs with exception details and retry options.

Web Interface

Visit /vantage to access the comprehensive monitoring dashboard:

Dashboard (/vantage) - Overview of your queue system:

Recent Jobs Table - Quick view of the latest 20 jobs with status, duration, and quick actions:

The Recent Jobs table appears on the dashboard showing:

Recent Batches - Track Laravel job batches with success/failure rates:

Jobs List - View and filter all jobs with advanced filtering options:

Visit /vantage/jobs to access the jobs list with powerful filtering capabilities:

Filter jobs by status, queue, job class, tags, and date range:

Job Details (/vantage/jobs/{id}) - Comprehensive job information:

Note: The dashboard requires authentication by default. Make sure you're logged in, or customize the viewVantage gate / VANTAGE_AUTH_ENABLED setting (explained below) if you need different behavior.

Retry Failed Jobs

Or use the web interface - just click retry on any failed job.

Programmatic Access

Vantage provides a convenient facade for easy programmatic access to queue monitoring data. The facade is automatically registered and ready to use:

Available Facade Methods:

Job Tagging

Jobs with tags (using Laravel's tags() method) are automatically tracked. Visit /vantage/tags to see:

Filter and view jobs by tag in the web interface.

Queue Depth Monitoring

Real-time queue depth tracking for all your queues. See how many jobs are pending in each queue with health status indicators.

Visit /vantage to see queue depths displayed with:

Performance Telemetry

Vantage automatically tracks performance metrics for your jobs:

Telemetry can be configured via environment variables (see Environment Variables section below).

Configuration

The config file should already be published during installation. If you need to republish it:

Main Settings

Enable/Disable Package

To disable the package entirely (useful for staging environments):

When disabled:

Perfect for testing in staging without affecting production data!

Multi-Database Support

If your application uses multiple databases, you can specify which database connection to use for storing queue job runs:

This ensures the vantage_jobs table is created and accessed from the correct database connection. The package automatically detects your database driver (MySQL, PostgreSQL, SQLite) and uses the appropriate SQL syntax for queries.

You can also point Vantage at a database of its own, so job history is kept separate from the data your application is working with. Define the connection in config/database.php like any other — it can live on the same server or a different one.

Other settings for high-volume queues:

Setting Effect
VANTAGE_STORE_PAYLOAD=false Stop storing job payloads — by far the largest column
VANTAGE_TELEMETRY_SAMPLE_RATE=0.1 Collect memory/CPU telemetry for 10% of jobs
VANTAGE_RETENTION_DAYS=7 Keep less history, combined with a scheduled vantage:prune
exclude_jobs / ShouldNotBeTracked Skip noisy, high-frequency jobs entirely

Authentication

Vantage protects the dashboard with Laravel's Gate system via the viewVantage gate.

Make sure your application has authentication set up (Laravel Breeze, Jetstream or your own implementation) unless you intentionally open the dashboard to everyone.

To customize access (e.g., only allow admins), override the viewVantage gate in your AppServiceProvider:

Want to keep the dashboard public but still record jobs? Either return true from the gate even for guests, or set VANTAGE_AUTH_ENABLED=false.

Exclude Jobs from Monitoring

if you want to exclude some jobs from being tracked by Vantage, you can add them to the exclude_jobs config array:

Or implement the 'ShouldNotBeTracked' class.

Testing

Using the Model Factory

Vantage includes a comprehensive model factory for creating test data in your application tests:

Running Package Tests

Run the test suite:

Commands

Retry Failed Job

Retry a failed job by its ID. The job will be re-queued with the same payload and settings.

Cleanup Stuck Jobs

Clean up jobs that are stuck in "processing" state. Useful for jobs that were interrupted or crashed.

Example:

Prune Old Jobs

Prune old job records from the database to free up space. This is essential for high-volume applications where the database can grow very large over time.

Options:

Examples:

Scheduling Automatic Cleanup:

Add this to your app/Console/Kernel.php to automatically prune old jobs:

For scheduled tasks:

Important Notes:

Environment Variables

Demo

Watch a brief demo of the Vantage dashboard in action:

Vantage Demo

Click the thumbnail above to watch the demo video on YouTube.

Contributing

Please see CONTRIBUTING for details on how to contribute to this project.

License

The MIT License (MIT). Please see License File for more information.


All versions of vantage with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2|^8.3|^8.4
illuminate/support Version ^10.0|^11.0|^12.0|^13.0
illuminate/queue Version ^10.0|^11.0|^12.0|^13.0
illuminate/events Version ^10.0|^11.0|^12.0|^13.0
illuminate/notifications Version ^10.0|^11.0|^12.0|^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package storviaio/vantage contains the following files

Loading the files please wait ...